Re: Batch Immediate CGI =/= Interactive monster?

From: Luke Gerhardt
I've got a CGI job with two threads

That's odd, the vast majority of CGI jobs in the world are single threaded. Did you write a multi-threaded CGI job? Or, are you referring to 2 single threaded jobs?

 They're listed as 'BCI'-type jobs

The Apache HTTP server itself is a multi-threaded job, but most shops start it with a lot more than just 2 threads; I think the default is 47 threads which handle communication between browsers and CGI jobs and perform actual streaming of content, both static and dynamic content to HTTP clients. We have a client that runs 2,000 threads normally, to support thousands of active users. Is that the job you're referring to?

Yesterday, a user complained of a 7 minute wait changing between two open sessions

That normally occurs when the client can't make a connection to the HTTP server, usually because other users have tied up all the connections, possibly because the HTTP server is maintaining persistent connections, according to the configuration directives used.

  each running at around 35%

This makes me suspect that you're actually talking about 2 jobs, as opposed to a single job running 2 threads. The 35% is based on what the job is doing, and you haven't given us any indication of what it might be doing. Serving a huge report? Downloading huge files? Running un-optimized queries against a huge database?

As Charles indicated, a job is a job is a job. The job type, BCI vs BCH vs INT makes no difference.