I've been using DPA to tune my SolarWinds. I've been annoyed by WRITE LOG as the chronic #2 wait time. All SQL volumes were already on all flash storage and being bound by the application there wasn't much else I could do to tune performance. After researching this type of wait I read an article about a SQL option called Delayed Durability. To me, the downsides are very minimal on a monitoring platform while the gains are significant.
Here's some reading about delayed durability.
https://sqlperformance.com/2014/04/io-subsystem/delayed-durability-in-sql-server-2014
Control Transaction Durability - SQL Server | Microsoft Docs
Using DPA to analyze waits for the same SQL server, same day of the week here are the results.
With delayed durability set to disabled. At 11 am peak total wait time is 17,000 secs.
With delayed durability set to forced. At 11 am peak total wait time is 3,500 secs a significant decrease in wait times.
The high activity at 12am is the Orion database maintenance.
The only change made was this option from disabled to forced. I didn't try allowed but that depends on the query having the durability option which I doubt.
I'm wondering why this option isn't part of the standard SolarWindsOrion installation. I couldn't find any mention of "delayed durability" on the SolarWinds support site either.
