RE: CPU/MI Timings -- MI400

× 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: [MI400] CPU/MI Timings
From: "Hall, Philip" <phall@xxxxxxxx>
Date: Fri, 10 Jan 2003 14:10:55 -0600
List-archive: <http://archive.midrange.com/mi400>
List-help: <mailto:mi400-request@midrange.com?subject=help>
List-id: MI Programming on the AS400 / iSeries <mi400.midrange.com>
List-post: <mailto:mi400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo.cgi/mi400>,<mailto:mi400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo.cgi/mi400>,<mailto:mi400-request@midrange.com?subject=unsubscribe>
Thread-index: AcK44pL2nRabPY1DRA2MG0JMwt8b2QAAL7qQ
Thread-topic: [MI400] CPU/MI Timings

> Walden, you are correct, won't make any difference.
> 

I beg to differ, in some cases it does make a difference. When you have a tight 
batch window, every second can count. When you ramp up to multiple concurrent 
jobs, a few seconds per job over hours counts too.

--phil

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: CPU/MI Timings , Leif Svalgaard

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.