Releases: spaghettidba/WorkloadTools
Releases · spaghettidba/WorkloadTools
My MI does not behave, but why?
Managed Instances want a totally different way of capturing CPU. Sigh.
Dates on the x
WorkloadViewer now shows dates on the x axis when you are analyzing a workload. When comparing two workloads it shows the offset in minutes instead.
Choose your Pool Size
Thanks to @thed000d you can now configure the MaxPoolSize in a SqlConnectionInfo object. This property can be set in the .json configuration files.
Prepare and execute
- Fixed bug in the replay of prepared statements. Now they work (at least they should)
- Added full join capabilities in workloadviewer. Previous versions used "baseline left join benchmark" as the source for the queries tab. Now it is a full join, so you can see some data even it the baseline contains no data for the selected time frame
Floating errors
Turns out regular expressions are tough. Who would have thought?
Prepared to be prepared
Small fixes, especially in handling of prepared statements.
- Fix for #91 (Extended events session is not removed from Azure SQL when TimeoutMinutes is set)
- Forced UploadIntervalSeconds to be in minutes
- Added more attributes to the connection strings (thanks @shellninja)
- Added checks to the input trace file before conversion
Expecting the Unexpected
- Fixed some bugs in replay.
- Added more error handling to keep replay alive
Event Sequence
- Fixed a bug in XE stream collection that prevented reading event_sequence
- Fixed a bug in performance counters collection that prevented cpu usage to be collected from Managed Instances
Context is king
This release contains two new features for the replay:
- The replay percent is displayed during execution
- The original event_sequence is added to the replay error messages, so that you can use it to locate the source command in the sqlite file, using the event_sequence column
These small additions should help you get more context when performing replays.
Easter Edition
Fixed a nasty bug with SynchronizationMode in Replay.
Now replay waits should follow original waits more closely.