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


  1.  Home
  2. MIDRANGE-L
  3. November 2007

RE: Quantify processing wasted by lots of little jobs

<snip>
Right now, there's 1800+ jobs waiting in the queue to run. CPU usage at
100%.

Seems like the CPU time spent creating the separate jobs would be better
used running the process
needed.

Ideally, I'd like to have the process using data queues and multiple
NEP's to handle the processing.
But it'd be a bigger job to allow multiple process to run at the same
time if it's even possible (the
limitation is not an iSeries application design issue, an AIX box is
involved).
</snip>

I would just write a first generation using a single data queue and see
what kind of performance you get. You might find that not having to
create and destroy jobs and being able to reuse resources is so fast you
do not need multiple jobs.

If you have 1800+ jobs waiting in the job queue, I say you definitely
have a problem.



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.