Priotiry
Priotiry
- Subject: Priotiry
- From: email@hidden
- Date: Sun, 8 Feb 2004 16:53:56 -0500 (EST)
Well I have a method which is very sensitive, and sharing processor time
can cause problems. Espcially if lots of apps are running and the app
caches something in the swap file.
Some of the issues I've found are cured by setting its priority to 1.0 at
it's most sensitive. And then back to it's original priority when it's
done.
What I am wondering is if it is possible to be a hair more aggressive at
the most sensitive of times. In other words, be modal, but modal system
wide like an old os 9 app. I know everyone hates that, but my other choice
is to close all open programs like an installer which I REALLY would not
want to even think about doing since it's just plain rude. When your
spooling data like live music or video to the harddrive you need to
dominate the processor especially on older machines to make sure you dont
get jumps, pops and clicks. An example is some older g4s experience
problems importing video over firewire with iMovie since iMovie does not
dominate the machine as it should during capture. Heck on os 9 toast was
so aggressive it would lock the clock until it was done.
Does this make sense?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.