-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Feature idea: perf analyzer behavior control #808
Comments
I do believe that Perf Analyzer supports something similar to what you are asking for via custom interval mode: |
We tried using this option through model analyzer, and got the following error:
We added it to the config.yaml in the following way:
Do you have any idea why this may happen? |
That is likely a bug :(. MA generally specifies the concurrency with every request and probably needs to be updated to not specify it when request-intervals are specified. I don't think it will be hard to fix. I'll try to reproduce and fix today. |
@Talavig Are you running into this from a brute search? Or quick search? |
We have originally encountered it using brute search, but we have tried using quick search as well and encountered the same error. |
Hello, I'm currently experiencing the same issue with model analyzer 24.02. Is there an update on the progress or a certain thing I need to do in the yaml to enable it? |
Hey, I as well try to use it and the bug still exists. Is there any news on an update or a solve to this issue? |
I am going to try to find time to get this fixed this week |
That will be awesome! Thanks for the update! Can you tell whether it'll come out as part of the 24.03 image? |
It will definitely not be 24.03. That being said, once I get a fix in you can always work with the main branch if you want it asap: |
Great! Thank you so much! |
This work is still in-progress |
Hey, is there an update? |
@tgerdesnv hey, is the feature done? |
We would like to suggest an idea we thought about and we do not think is currently available in model analyzer or perf analyzers:
When using model analyzer, we want to replicate the behavior of the prod environment when testing. For example, we want to send a lot of requests at once (a local spike of usage), or a gradual, more controlled increased in requests in specific timestamps, or any other pattern of usage.
We would like to propose the following solution: add a field in the config file with that can take on of two kinds of values: either keywords that represent different usage behaviors like spikes or gradual increase, or a path to a file. This file can contain a json generated by the customer with specific "directions" to the wanted behavior. For example, for 3 seconds send x request and then send a spike of requests.
Is such a feature possible to implement? It can be very valuable to us.
The text was updated successfully, but these errors were encountered: