>Time slices can control some things, but do you want an interactive job
to
>have to wait for a batch job to complete its (comparatively long) time
slice
>before it can run? 

But won't the job also yield as soon as it goes into a long wait? 

And since IO is a long wait, unless you're calculating something very
complex that doesn't include IO (SETI@HOME?) the batch job will yield
LONG before it eats up it's time slice, no?

-Walden

------------
Walden H Leverich III
President & CEO
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 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.