D
dbeavon
Guest
So I'm hearing that -Bp doesn't allow me to reset/flush my buffers after a client disconnects. The buffers stay in memory. (Nor does this help with the ultimate goal of testing the performance of reads when they are going all the way back to disk.). It might be that we have some pretty slow I/O hardware. But I've often noticed that some ABL code, like certain reports, will execute *extremely* slow if run once in a day, and will be fast on subsequent executions (every ten minutes). There should be a way to troubleshoot and optimize the *first* execution of the report, and in that way isolate the I/O hardware issues that lie beneath the database. Today the only good way to troubleshoot the *first* execution is to stop and restart the entire OE database. In the Windows world we use an I/O tool called "sqlio" for isolating and troubleshooting hardware. And insofar as SQL server itself is concerned, we can use DBCC DROPCLEANBUFFERS whenever we need our database reads to go all the way back to the disk. I am still absolutely convinced that there is a secret command for easily flushing out the OE buffer pools (ie. removing clean buffers from the "LRU chains" for -Bp and -B). I *really* wish someone would tell us what it is. We promise to use it in development and not in production. Insofar as my initial question goes, are there any thoughts on the likelihood of a new service pack (11.6.4) given the -B2 issues? I'm hearing that -B2 is a fairly popular feature (or at least it was before it broke). And I think we were specifically advised to use it with "object level assignments" that reference the specific tables that would benefit the most. Can someone tell me how many severe bugs need to be found before an OE service pack is made available? I'd rather stay on 11.6.3 for testing and wait to do a production upgrade after 11.6.4 is available.
Continue reading...
Continue reading...