|
Hello Nathan, You wrote: > To support 40 concurrent users, you probably need at least 40 HTTP Server >threads. However, that may lead to 40 active BCI jobs. Each one of those >jobs could activate your 40 CGI programs. That could lead to 1600 CGI >activations if the CGI programs run under a named activation group. 1600 >active CGI instances may put a burden on OS/400 memory management. Surely that's only the case if you put each CGI program in its own named activation group? If the CGI programs are part of the same application why would they not be in the same activation group? Thus one activation group per BCI job. That should be manageable on any size AS/400. Persistent CGI requires named activation groups -- not that the names be different. Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 mailto: shc@flybynight.com.au \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.