no guarantee that they will be used appropriately if the thread scheduler is configured "wrongly."
And it happens even under non-severe loading conditions. You say "typically 8" but what are the upper bounds of # of active threads?
I'm just tossing out an idea, but the fact that you see the delays only 4-5 times a day suggests that thread scheduling is not the issue.
I think the only way you can really be sure that the delay/download time is caused by external factors (remote webserver saturation or network issue) is to run something like Ethereal or tcpdump. That would
tell you when the initial request goes out over the wire and when you receive a response back. That's about as close to a smoking gun as I can imagine.
Another thing you could do is to include a webserver on your LAN as part of the polling and see if you ever get a significant delay over an extended period of time.
Tony
On Thursday, July 3, 2003, at 01:47 PM, Michael Mattox wrote:
What I see is that normally I get download times 150ms and then
occassionally (4-5 times a day) I see a download time of 3000ms. It happens
to the majority of the websites, so I do not believe it's a particular site.
So it must be either my application, or the network. My application uses a
thread pool and always has multiple threads running (typically 8 at a time
on a 4 CPU machine that's also running tomcat and Postgres), and I've seen
that at exactly the same time a website has a 3000ms download time several
others have normal 150ms times. So this seems to rule out the network. I
set my threads to be all MAX_PRIORITY to minimize the interruptions. Are
there any other explanations? Any ideas what I can do about it? My current
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
