× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



oops sorry, I meant to forward to someone else, not the list.

> -----Original Message-----
> From: Scott Mildenberger [mailto:Smildenber@Washcorp.com]
> Sent: Friday, January 25, 2002 12:28 PM
> To: 'web400@midrange.com'
> Subject: RE: [WEB400] performance of cgi-interactive programs
>
>
> You might want to experiment with this sometime, especially
> the persist
> timeout and maybe starting more threads.  May help, may not.
>
> Scott
>
> > -----Original Message-----
> > From: Nathan M. Andelin [mailto:nandelin@relational-data.com]
> > Sent: Friday, January 25, 2002 11:49 AM
> > To: web400@midrange.com
> > Subject: Re: [WEB400] performance of cgi-interactive programs
> >
> >
> > From: "Mark A. Manske" <mmanske@minter-weisman.com>
> > > In response to a few questions everyone has about our
> > > "set-up" here...
> >
> > Mark,
> >
> > On my little 170-2290 (73 CPW), I activate 40 HTTP Server
> > threads.  I also
> > use the "Keep-Alive" header in connection with the following
> > configuration
> > directives:
> >
> > PersistTimeout 2 minutes
> > MaxPersistRequest 40
> >
> > It improves network performance.  The default behavior is
> for the HTTP
> > server to drop the connection after serving a page.  You
> > might try something
> > similar to test performance.  Your pages reference quite a
> > few small image
> > files.  The pages also provide links to PDF files.  Serving
> > them with only 5
> > active HTTP server threads and dropping the connection after
> > each request
> > may impact your users significantly.
> >
> > Performance tuning with CGI can be a balancing act.  An
> > active connection
> > puts a lock on one of the HTTP server threads.  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.  It's a balancing act.
> > It sounds like
> > you may have plenty of memory.
> >
> > Good luck,
> >
> > Nathan M. Andelin
> > www.relational-data.com
> >
> >
> > _______________________________________________
> > This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> > To post a message email: WEB400@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> > or email: WEB400-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/web400.
> >
> _______________________________________________
> This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> To post a message email: WEB400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> or email: WEB400-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/web400.
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.