-
Task
-
Resolution: Done
-
L3 - Default
-
None
-
None
-
Not defined
Context:
With OPT-5953, we have added a basic zeebe data generator job to generate data we can use in import performance tests. We can iterate on this generator to improve it by:
ability to create different data snapshots, eg one 1M instance one for import performance tests and one 100M instance dataset for query performance testsability to select name/filter of snapshot as job parameterdone
- consider adding manipulation of when instances are exported to create zeebe record indices spread over several days
consider adding the job worker count as a configurable parameterdone- consider adding more variety to deployed instances/definitions
- extract methods shared between zeebe data generation and import performance into shared jenkins lib (eg ES snapshot related code)
switch to stable node pool to avoid issues with longer running jobsdone
AT:
- tbd depending on which of the above are to be implemented, might also extract tasks into separate tickets
This is the controller panel for Smart Panels app
1.
|
Add parameter for jobworker count to zeebe data generation |
|
Done | Unassigned |
2.
|
Add ability to store/create multiple different snapshots |
|
Done | Unassigned |
[OPT-6049] Zeebe Data Generation Improvements
Labels | Original: current_release |
Description |
Original:
*Context:*
With * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * consider adding the job worker count as a configurable parameter * consider adding more variety to deployed instances/definitions *AT:* * tbd depending on which of the above are to be implemented |
New:
*Context:*
With * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * consider adding the job worker count as a configurable parameter * consider adding more variety to deployed instances/definitions * extract methods shared between zeebe data generatio and import performance into shared jenkins lib (eg ES snapshot related code) *AT:* * tbd depending on which of the above are to be implemented |
Description |
Original:
*Context:*
With * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * consider adding the job worker count as a configurable parameter * consider adding more variety to deployed instances/definitions * extract methods shared between zeebe data generatio and import performance into shared jenkins lib (eg ES snapshot related code) *AT:* * tbd depending on which of the above are to be implemented |
New:
*Context:*
With * ability to create different data snapshots, eg one 1M instance one for import performance tests and one 100M instance dataset for query performance tests * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * consider adding the job worker count as a configurable parameter * consider adding more variety to deployed instances/definitions * extract methods shared between zeebe data generation and import performance into shared jenkins lib (eg ES snapshot related code) *AT:* * tbd depending on which of the above are to be implemented, might also extract tasks into separate tickets |
Description |
Original:
*Context:*
With * ability to create different data snapshots, eg one 1M instance one for import performance tests and one 100M instance dataset for query performance tests * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * consider adding the job worker count as a configurable parameter * consider adding more variety to deployed instances/definitions * extract methods shared between zeebe data generation and import performance into shared jenkins lib (eg ES snapshot related code) *AT:* * tbd depending on which of the above are to be implemented, might also extract tasks into separate tickets |
New:
*Context:*
With * ability to create different data snapshots, eg one 1M instance one for import performance tests and one 100M instance dataset for query performance tests ** ability to select name/filter of snapshot as job parameter * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * consider adding the job worker count as a configurable parameter * consider adding more variety to deployed instances/definitions * extract methods shared between zeebe data generation and import performance into shared jenkins lib (eg ES snapshot related code) *AT:* * tbd depending on which of the above are to be implemented, might also extract tasks into separate tickets |
Labels | New: current_release |
Description |
Original:
*Context:*
With * ability to create different data snapshots, eg one 1M instance one for import performance tests and one 100M instance dataset for query performance tests ** ability to select name/filter of snapshot as job parameter * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * consider adding the job worker count as a configurable parameter * consider adding more variety to deployed instances/definitions * extract methods shared between zeebe data generation and import performance into shared jenkins lib (eg ES snapshot related code) *AT:* * tbd depending on which of the above are to be implemented, might also extract tasks into separate tickets |
New:
*Context:*
With * ability to create different data snapshots, eg one 1M instance one for import performance tests and one 100M instance dataset for query performance tests ** ability to select name/filter of snapshot as job parameter * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * consider adding the job worker count as a configurable parameter * consider adding more variety to deployed instances/definitions * extract methods shared between zeebe data generation and import performance into shared jenkins lib (eg ES snapshot related code) * switch to stable node to avoid issues with longer running jobs *AT:* * tbd depending on which of the above are to be implemented, might also extract tasks into separate tickets |
Description |
Original:
*Context:*
With * ability to create different data snapshots, eg one 1M instance one for import performance tests and one 100M instance dataset for query performance tests ** ability to select name/filter of snapshot as job parameter * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * consider adding the job worker count as a configurable parameter * consider adding more variety to deployed instances/definitions * extract methods shared between zeebe data generation and import performance into shared jenkins lib (eg ES snapshot related code) * switch to stable node to avoid issues with longer running jobs *AT:* * tbd depending on which of the above are to be implemented, might also extract tasks into separate tickets |
New:
*Context:*
With * ability to create different data snapshots, eg one 1M instance one for import performance tests and one 100M instance dataset for query performance tests ** ability to select name/filter of snapshot as job parameter * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * consider adding the job worker count as a configurable parameter * consider adding more variety to deployed instances/definitions * extract methods shared between zeebe data generation and import performance into shared jenkins lib (eg ES snapshot related code) * switch to stable node pool to avoid issues with longer running jobs *AT:* * tbd depending on which of the above are to be implemented, might also extract tasks into separate tickets |
Description |
Original:
*Context:*
With * ability to create different data snapshots, eg one 1M instance one for import performance tests and one 100M instance dataset for query performance tests ** ability to select name/filter of snapshot as job parameter * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * consider adding the job worker count as a configurable parameter * consider adding more variety to deployed instances/definitions * extract methods shared between zeebe data generation and import performance into shared jenkins lib (eg ES snapshot related code) * switch to stable node pool to avoid issues with longer running jobs *AT:* * tbd depending on which of the above are to be implemented, might also extract tasks into separate tickets |
New:
*Context:*
With * ability to create different data snapshots, eg one 1M instance one for import performance tests and one 100M instance dataset for query performance tests ** ability to select name/filter of snapshot as job parameter * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * -consider adding the job worker count as a configurable parameter- done * consider adding more variety to deployed instances/definitions * extract methods shared between zeebe data generation and import performance into shared jenkins lib (eg ES snapshot related code) * switch to stable node pool to avoid issues with longer running jobs *AT:* * tbd depending on which of the above are to be implemented, might also extract tasks into separate tickets |
Description |
Original:
*Context:*
With * ability to create different data snapshots, eg one 1M instance one for import performance tests and one 100M instance dataset for query performance tests ** ability to select name/filter of snapshot as job parameter * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * -consider adding the job worker count as a configurable parameter- done * consider adding more variety to deployed instances/definitions * extract methods shared between zeebe data generation and import performance into shared jenkins lib (eg ES snapshot related code) * switch to stable node pool to avoid issues with longer running jobs *AT:* * tbd depending on which of the above are to be implemented, might also extract tasks into separate tickets |
New:
*Context:*
With * ability to create different data snapshots, eg one 1M instance one for import performance tests and one 100M instance dataset for query performance tests ** ability to select name/filter of snapshot as job parameter * consider adding manipulation of when instances are exported to create zeebe record indices spread over several days * -consider adding the job worker count as a configurable parameter- done * consider adding more variety to deployed instances/definitions * extract methods shared between zeebe data generation and import performance into shared jenkins lib (eg ES snapshot related code) * -switch to stable node pool to avoid issues with longer running jobs- done *AT:* * tbd depending on which of the above are to be implemented, might also extract tasks into separate tickets |