Re: IBM i and Java -- 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: IBM i and Java
From: Charles Wilt <charles.wilt@xxxxxxxxx>
Date: Thu, 1 Dec 2016 08:30:04 -0700
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/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Thu, Dec 1, 2016 at 7:55 AM, Paul Nelson <nelsonp@xxxxxxxxxxxxx> wrote:

(You'd be dumbfounded by the memory and disk spikes caused by their index
building.)

That's not related to Java...the same functionality (and apparent lack of
optimization) in a 5250 app would cause the same spikes.

Assuming they are running newer hardware and have enough memory, Java
should run fine.

Charles

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: IBM i and Java , Paul Nelson
Re: IBM i and Java , Rob Berendt

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.