-
Notifications
You must be signed in to change notification settings - Fork 54
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
Performance Improvement #142
Conversation
a-teece
commented
Oct 26, 2023
- Improved the PreciseDelay method to enhance accuracy and significantly decrease CPU load.
- Fix percent completed message.
- Handle "stopped" in more places to try and fix shutdown failures (still doesn't shutdown correctly after pressing ctrl-c when using ReplayConsumer).
Handle "stopped" in more places to try and fix shutdown failures. Improve sleep accuracy using a sliding scale of sleep times relative to the desired sleep.
Great job! Thank you for your contributions! |
I haven't actually changed that. You were already closing / opening the connection with no regards to transactions. All I have done is remove the delay for the "next" command in such a scenario. The reasoning is that a developer will likely Open connection think time Open connection So the replay should be trying to replicate the "think time", but not the time between Open connection/Run Command. This is likly tiny (so not really replicatable given accuracy challenges). Theoretically if there is a SQL Transaction then the original code could not have closed/opened the connection. If it was a DTC transaction, which would allow the close/open (our app does this) then I don't believe the trace has captured that and none of the code replicates that. So I'm not sure if you have a transaction problem anyway. |
Ah I see. Maybe I was just thinking about it but I never coded it correctly. |
It is certainly being helpful now. We're comparing a workload of SQL on AWS EC2 vs Azure Managed Instance. Using this tool to prove the performance goals can be met of a migration. |
This is great news, thanks for the feedback! |