Re: Batch Immediate CGI =/= Interactive monster?

From: Luke Gerhardt
I was hopeful that there was a clear explanation I can pass on that
explains 1) why these jobs chew up a lot of %,

I had a colleague who wrote JavaScript to poll the server which for some unknown reason fired off so many requests per second that he caused his own denial of service attack. Maybe the timer was messed up. I'm not sure. This would show up in the HTTP server logs.

2) what would happen when an interactive job came on the scene

needing % for itself.

I haven't ever seen a case where HTTP jobs caused a delay in establishing a 5250 session. If that were the case, I'd still suspect a bottleneck at the socket level, because the 35% cpu utilization wouldn't cause it.