Jobs or Threads? -- JAVA400-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: Jobs or Threads?
From: "Brad Stone" <brad@xxxxxxxxxxxx>
Date: Mon, 25 Feb 2002 12:42:16 -0500
List-archive: <http://archive.midrange.com/java400-l/>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/java400-l>,<mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/java400-l>,<mailto:java400-l-request@midrange.com?subject=unsubscribe>

Just thinking outload here.

Let's assume I have an appliation that I want to run many
times simultaniously.  Assuming I'm running the aplicate on
the 400, what would be "better".

1 - Running the application in multiple jobs (ie submitting
the job x times into QSYSNOMAX or something similar)

2 - Running many instances of the apllication using Java
threads?

I'm guessing it really won't make much of a difference
unless job resource allocation comes into play.

Bradley V. Stone
BVS.Tools
www.bvstools.com

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.