Hi there,

we are encountering another weird problem: a (very) long lag awake-time.

We happen to log the application-level awake and some of the component-level 
awakes. Normally, the latter happen just a couple milliseconds from the former. 
Nevertheless _sometimes_ when the load gets higher and more R/R loops run 
concurrently, this lag grows up to a complete nonsense — tens or, in the worst 
cases, hundreds of seconds (between Application.awake and some Component.awake).

The most obvious answer that either the session-level awake or some of the 
non-logged component-level awakes might take an eternity upon a higher load is 
still an open possibility, but quite improbable one: we have profiled our 
application when the problem did happen with a smaller load, a couple of times 
the lag grew up to about 5-7 s, and still none of the awake methods ever took 
more than 40 ms.

Has perhaps anyone here encountered a similar problem and might suggest a 
solution or at least a reasonable way to find the culprit?

Thanks and all the best,
OC

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to