× 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.


  • Subject: Re: JAVA400-L Digest V2 #57
  • From: "Nathan M. Andelin" <nathanma@xxxxxxxxx>
  • Date: Fri, 2 Mar 2001 08:06:34 -0700

David, I wasn't running websphere in that http server instance.  Instead, I
used a home-grown plug-in that provided a data queue interface to the rpg
program.

----- Original Message -----
> Date: Fri, 02 Mar 2001 05:25:17 -0700
> From: "David Morris" <dmorris@plumcreek.com>
> Subject: Re: RE: Java and CPU
>
> Nathan,
>
> That is amazing.  I had a system with exacly the same configuration,
> and the HTTP server used 5% of the CPU when idling 24/7 on V4R4,
> on V4R5 it went down to 3%.  It would not run WebSphere 3+ acceptably
> to I upgraded to a 270 that does OK with WebSphere and HTTP is
> almost undetectable.
>
> David Morris


Brad, I'll try to do a little more research on this.  Maybe the BCI jobs do
add in the CPU of the CGI.


----- Original Message -----
> Right, I included the BCI Jobs.  The BCH job in my first example is simply
> serving HTML.  So, if we leave the BCH job out, it makes the different
even
> more off.
>


+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---

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.