D
dbeavon
Guest
The other day I was trying to get the fastest possible response out of a SQL broker for OE. My plan is to use this as an indication of whether the database was online or not. In addition to making a SQL92 database connection, I wanted a query response to be returned from the database broker. The fastest end-to-end response I could get out of OE was unimpressive (~150 ms) and I only attained this when the client code was running in a very tight loop. For my query I used " SELECT * FROM sysprogress.syscalctable ". The vast majority of that time was consumed by a *CPU* bottleneck (in "_sqlsrv2" on HP-UX). I think this could be a reasonable example of how the application software can become a massive bottleneck in an operation that might otherwise be a matter of sending a few network packets back and forth. I suspect that it was less than 1 ms that was actually spent waiting on network resources, and all the remaining delay was because of a "storage" engine bottleneck. (Granted no actual disk was ever used - that would have added even *more* overhead that was not network related.)
Continue reading...
Continue reading...