D
dbeavon
Guest
Will the number of timeslices (for the same set of queries) change depending on whether there are other co-habiting clients that are making concurrent query requests? In other words if client A did all its queries from 8AM to 9AM and client B did all its queries from 9AM to 10AM then how would the number of timeslices compare to a scenario where A and B both started their queries at 8 AM and attempted to run them concurrently? I just want to know if my metric will be valid. In order to measure the amount of contention on the timeslices of a server ( _mprosrv ), I was going to use a metric that takes Server-QryRec and divides by _Server-TimeSlice. This metric assumes that the timeslices would be much higher (relative to the number of queries) in a server that accommodates lots of clients at a time. I'm hoping the assumption is valid. I suppose I am being influenced by the "interrupt" terminology in the OEE console. If a client isn't being "interrupted" by other clients then the number of timeslices should be lower (relative to the number of queries that are executed). But that is a very literal interpretation of an "interruption". Perhaps the number of "interrupts" are always the same, and not determined by whether there are any other clients that are doing the "interrupting".
Continue reading...
Continue reading...