On 6 ene, 20:01, Lloyd Zusman <[EMAIL PROTECTED]> wrote: > It seems that the original writer of the app had set this interval to a > high value in a part of the code that I overlooked until you mentioned > this right now. > > [...] once one of the big > number-crunching threads gets control, it starves out the monitoring > threads, which is not a good thing for my app ... or at least it did > so with the original large checkinterval.
This is why such settings should be in a configuration file or in a prominent place in the application... I had a program where, deep in an unknown function, the original coder changed the process priority - with no valid reason, and in any case, that should be an application-level setting. It was hard to find why, after doing such and such things, the system responsiveness were so slow. -- Gabriel Genellina -- http://mail.python.org/mailman/listinfo/python-list