RE: Saving the System i: Fight Rather Than Switch -- MIDRANGE-L

× 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: Saving the System i: Fight Rather Than Switch
From: "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>
Date: Wed, 13 Dec 2006 14:27:11 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

To fully utilize all 16 processors, you'll probably 
need to deploy your applications across about 32 
instances of Websphere


Huh? Care to explain that? Are you saying WebSphere won't take advantage
of multiple processors? That can't be. I would expect one instance of
WebSphere, running one copy of my app to be perfectly happy spreading
the load across multiple CPUs. Am I nuts?

-Walden

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.