× 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

I know from personnel experience that the difference can be huge
although as the processors have gotten faster, the difference is not as
much.

We had a shipping print job and the programmer wrote it to submit three
jobs to print three documents. Because of all the time spent starting
and stopping jobs by the end the day shipping was still waiting for a
documents.

My boss finally allowed me to rewrite as a data queue server and time
dropped to a second to get out all three documents.

I am dealing with the same thing from a vendor product on my current
system. It submits hundreds and hundreds of jobs cluttering up
everything but the 520 is so fast that it does not seem to effect
processing time although technically it should. Nothing takes more
resources and time than creating and deleting jobs on the AS/400.

Using a data queue server is always a good idea.

Probably the question you want to ask is how long are users waiting and
are other things not getting done?



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.