Paul, > > Are you running SuperServer, Classic or SuperClassic? > > It is super server, although this should not make any difference. The code > that collects the stats is at a very low level. It is related to when the O/S > system calls are made to physically read/write to disc.
With cooperative garbage collection, it is not the active request which performs the garbage collection, but a background one. As such, it may be the case that the background cleanup IO is being attributed to the current request. If the database had a lot of bad versions, then the amount of IO would be larger than the amount of IO directly related to the current statement. I would retry a couple of your tests using Classic and see what the numbers tell. > > Have you considered the effect of garbage collection? > > How would that have an effect? See above. Sean ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
