|
From: "James Rich" <james@eaerich.com> > And if you're *really* smart you will use the sleep() system > call so you don't waste cpu cycles burning through loops. And taking it to one more level, how about letting the OS divide available CPU time according to job priority and job time slice parameters? Move away from performance governors? Upgrade the hardware, or divide the work across multiple systems when performance gets bad? Nathan M. Andelin www.relational-data.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.