It seems reasonable that (de)-serialization could be done in threaded fashion and then just block on the (read) write itself.
That would explain the utilization which is suspect is close to 1/N where N is the number of processors. On 12/12/07 2:07 PM, "Jason Venner" <[EMAIL PROTECTED]> wrote: > Our theory is that the serialization time (not the disk write time) and > the deserialization time (not the disk read time) is the bottleneck. > I have some test code nearly ready to go, if it changes the machine > utilization on my standard job, I will let you know...
