![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 11 to 11 of 11 total |
![]() |
Tue, Jul 24 2007 11:25 AM | Permanent Link |
Dave Harrison | mattjones@cix.co.uk (Matthew Jones) wrote:
> My take on this, FWIW, is that disk access is involved. What happens is > that DBISAM will make an OS call, and try to read from disk. That causes a > small pause to the thread since the data has to be read, and another > thread will take over the processor. When that thread finishes, the > scheduler will awaken the DBISAM thread again, and give it to the next > free processor. The disk thread may still be running, so it switches > context to the other processor. Hence it flips across the processor each > time. > > /Matthew Jones/ Matthew, It looks like you're right. If I assign my app to use only one processor, the processor is pegged at 100% and the other processor drops to near 0. If I switch it back to using 2 processors, both processors are around 50%, so it looks like it is just trading work (my app) between processors so one processor is never overtaxed. Neat. Dave |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Thursday, July 10, 2025 at 10:36 PM | Privacy Policy![]() © 2025 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |