I've got a CGI job with two threads, each running at around 35% when
/nothing else /is active. They're listed as 'BCI'-type jobs. This CGI
system has been in place for about 6 months. Yesterday, a user
complained of a 7 minute wait changing between two open sessions on his
relatively new Windows PC and concerned persons are pointing at this CGI
system as being a possible culprit due to it having high %s when it's
running alone.
I've tried to delay the notion of scrapping it and writing a PC program
by manually dropping the priority on those jobs to 8. But...how can I
explain it using so much of the system? What are the effects of this
type of job, compared to a full-bore interactive job chewing up 70% of
the system?
Thanks!!
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
