Batch Queue Management and the Magic of ‘2’

Trying to run too many simultaneous Concurrent Manager jobs hurts system performance. The temptation to make this error is powerful: the Concurrent Manager lets you specify any number of queues that you want, and certainly your intuition might tell you that more queues might yield better batch throughput. But executing more than about two simultaneous batch jobs on a CPU degrades response times for everyone and actually reduces the total amount of work the system can do for your business. This paper explains the science behind why the number 2.0 is the magical key to batch queue management that maximizes performance for everyone.

This article is marked © 2000 by Hotsos Enterprises, Ltd., but the current copyright owner is Cary Millsap.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.