-
Notifications
You must be signed in to change notification settings - Fork 97
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
Generate synthetic manifests for performance tests #1495
base: main
Are you sure you want to change the base?
Conversation
a174eb8
to
66aa80b
Compare
66aa80b
to
ab4a8b5
Compare
85662b2
to
7357bb9
Compare
ab4a8b5
to
43468b2
Compare
* Minimize the number of parameters required. | ||
|
||
Notes: | ||
* The synthetic manifest groups semantic models into two types - ones containing measures, and others containing dimensions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose this still captures the relevant behavior from production models, so it's fine? Is there anything extra we'd able to test by relaxing this and creating "mixed" models?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same question for the other constraints: you can reach all measures via all dimensions etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So those are simplifications to make it easier to generate semantic models and to make it easier to generate queries for metric. Mixed models would make it mimic production better, but I didn't think the added complexity would flesh out any performance cases that much better.
This PR adds a few classes to generate a synthetic manifest. The synthetic manifest can then be used to profile performance and scaling behavior.