On 8/31/06, Joel Cass <[EMAIL PROTECTED]> wrote: > I'm talking more about what CF was *designed* to do. Adobe would have > realised that releasing a CFSLEEP tag might cause some users to complain > about the server hanging all the time when really it's the excessive use of > the tag which is the problem.. So they never released this "function" within > "CF"..
Servers 'hang' for many reasons. The classic 'hang' is when you've got 100's of processes doing long bouts of intense file I/O. Behind the scenes a file I/O request to the OS will 'sleep' the requesting process. The filesystem will 'interrupt' the OS, which then wakes the requesting process. This mechanism is the same for the sleep command. Sleep sets up a timer in the OS and the OS will 'sleep' the requesting process. When the timer expires, the OS is 'interrupted' and the sleeping process is awakened. I hope you're not saying that application servers as single threaded? Every request runs in it's own thread, so sleep a thread will allow other threads to run. It is possible to have a heavily loaded machine be effectively idle because every thread and process is waiting for their request to complete. Chris -- Chris Velevitch Manager - Sydney Flash Platform Developers Group m: 0415 469 095 www.flashdev.org.au --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie -~----------~----~----~----~------~----~------~--~---
