Re: CPU bound

>>>>> "MG" == Mladen Gogala <mladen.gogala@vmsinfo.com> writes:

MG> Good time accounting is the most compelling reason for having a wait
MG> event interface, like Oracle. Without the wait event interface, one
MG> cannot really tell where the time is spent, at least not without
MG> profiling the database code, which is not an option for a production
MG> database.

And how exactly, given that the kernel does not know whether the CPU is
active or waiting on ram, could an application do so?

-JimC
--
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6