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



Run your overnight processing if you have any. Run that nasty batch job
that convinced management to spring for the upgrade in the first place.

Queries and stress tests are all well and good if a benchmark is what you're
after, but if you want numbers for management, give them old box/new box
comparisons for your existing business processes. Nothing will make them
feel better than to say that the upgrade reduces a process cycle by 30% (or
whatever).

It also has the added benefit of setting realistic expectations. If the new
box is 250% faster on CPU benchmarks but only 40% faster on your particular
workload (due to other dependencies like DASD), then the only number that
matters is the 40%.

On Wed, Dec 15, 2010 at 8:31 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Point a web stress tool at some of your web applications. That's something
that
can test multiple processor cores in parallel & drive CPU to 100%.

-Nathan



----- Original Message ----
From: Josh Diggs <JDiggs@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Wed, December 15, 2010 2:45:02 PM
Subject: Performance testing

We've just installed a new 720 box and I am looking for a way to
demonstrate the
performance difference between it and our old 525. Can anyone suggest a
simple
method to evaluate the performance difference without worrying too much
about
the difference in load etc. I don't need anything too elaborate, just a
method
that might give me some practical measure of the difference in horsepower.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.