Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Perf stresstest workload #124

Open
wants to merge 22 commits into
base: main
Choose a base branch
from

Conversation

anjagruenheid
Copy link
Contributor

Custom workload that executes performance stress tests by a) increasing the number of joins present in a base query and/or b) query padding. These augmented tasks are executed concurrently by duplicating sessions (if specified by the user). This PR introduces the end-to-end workflow for this workload pattern and addresses the following fixes to the codebase:

  1. SQLParser now outputs strings rather than StatementExecs for a cleaner separation of functionality.
  2. Event identifiers have been modified to essentially showcase the hierarchy. For example, the first statement in file a, part of task t and executed in session 1 is now identified as 1;t;a;0.
  3. Adds a layer of abstraction for custom task execution to be consistent with the argument implementation.

** This PR does not yet contain sufficient test cases and will not be committed until those are added. **

@jcamachor
Copy link
Contributor

@anjagruenheid , could we split the changes that refactor/move CustomTaskExecutor into a new PR that we could try to merge as soon as possible (since maybe other aspects of this PR need further discussion)? I'm working on #139 and there will be some merge conflicts otherwise. Thanks

@jcamachor jcamachor force-pushed the main branch 3 times, most recently from b3b87eb to 95c3aa4 Compare January 22, 2024 23:22
@jcamachor jcamachor force-pushed the main branch 3 times, most recently from 44a31f1 to 13a6b2c Compare January 23, 2024 01:05
@jcamachor jcamachor force-pushed the main branch 2 times, most recently from 868d4f8 to ff310c5 Compare April 30, 2024 18:18
@jcamachor jcamachor force-pushed the main branch 3 times, most recently from 4def705 to 7876be3 Compare July 10, 2024 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants