|
Just for clarification it is actually around 50 programs (there are a bunch in the sign-on secured portion of the site that you never see...) We shut down and restart the HTTP server every night for multiple reasons. First of all, it resets the number of active Server Instance jobs. Second, it in effect deletes all the CGI activation groups so that they get re-initialized at the first call of the day. Finally, during the 120 seconds that it is down we do statistical compilation and collection. Joel R. Cochran Director of Internet Services VamaNet.com 800-480-8810 (va toll free) 540-885-8050 (phone) 540-886-1589 (fax) www.vamanet.com mailto:custservice@vamanet.com >-----Original Message----- >From: Nathan M. Andelin [mailto:nandelin@relational-data.com] >Sent: Wednesday, October 03, 2001 8:27 PM >To: midrange-l@midrange.com >Subject: Re: CGIDEV2 performance versus Net.Data > > >> From: "Mel Rothman" <mel@rothmanweb.com> > >> Where are you measuring Relational Web's CPU? In the message >> server? In the application server(s)? Both? It seems that both is >> what should be measured. > >Yes, both. Just to confirm, the CPU time for the >Relational-Web message >server is reflected in the HTTP Server's BCI job. The CPU time for the >application server is reflected in a separate job. There's >also a 3rd Job I >call the "switch" used to route and load-balance requests. I >add that time >too. > >For Easy400 and Net.Data I count CPU time for both HTTP Server >BCI and BCH >Jobs. > >> What about response time comparisons? > >I don't have a good way to measure it. Over my 128 kb router >it's hard to >tell ;( > >Your other comments Mel, have convinced me that named >activation and CGI go >hand and hand, for high use scenarios. But Joel Cochran >apparently shuts >down restarts the HTTP server daily to reclaim CGI resources. >I think his >application consists of about a dozen CGI programs. What >about sites that >deploy hundreds? Shut down and restart every couple hours? > > >Nathan M. Andelin >www.relational-data.com > > >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) >mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
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.