What is the status of DB_PROPERTY CurrRead and CurrWrite?

[Breck_Carter]

This question is prompted by the new server properties introduced in Version 17...

CurrRead The current number of file reads that were issued by the database server, but that have not completed yet.

CurrWrite The current number of file writes that were issued by the database server, but that have not completed yet.

The addition of those properties implies that the database properties of the same name may in fact be reliable; is that true?

The question is important because historically the CurrIO database property has been so wildly inaccurate as to be completely useless.

Tue, Nov 8, 2011 at 10:00 AM... You are correct. Dan had already identified this as an issue with his Fuji testing: Yes, I recently found out that the CurrIO stat is completely bogus; it sits in a layer of the code that has many callpaths and not all are properly accounted for.

So... can we now trust the database properties CurrRead and CurrWrite in SQL Anywhere 17?

How about Version 16, and earlier releases?

[Former Member · Accepted solution]

There was a change to address the inaccuracies of these I/O counters. This fix made it into the 17 release but not to branches before that.

[Breck_Carter · Accepted solution]

Hooray!

Now I can un-comment the code in Foxhound, at least for V17 target databases, to display CurrIO etcetera... incomplete I/O can be a bad sign for performance.