× 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: How are CPU Speed and Overall CPW Related?
  • From: Jon.Paris@xxxxxx
  • Date: Wed, 2 May 2001 16:20:42 -0400

Nathan, while I doubt it will erase all of the time difference, the code in
your example is not doing anything like the same thing.

Change theShorter to a constant and replace the %Trim with a simple Eval or
move with pad and then you've got a closer match.  The way it is right now
the Foxpro should be treating theShorter as a constant and there is no
trimming going on anywhere.

Another RPG alternative would be to set a variable called space up (50 long
initialized to blanks) and then substring that onto a constant.  Which is
much closer to what you are doing in FoxPro.

One more option would be to run the optimizer on the RPG code - it may
eliminate some of the code.

None of this matters worth a darn though because real programs don't simply
wizz round in circles doing nothing.  CPW is intended to be a measure of
the overall "real" workload the system can handle.  That includes User I/O,
disk access, etc.  which on a 400 is mostly carried on by secondary
processors and not by the main CPU.  If I have a lot of users, an
additional IOP will probably improve the throughput of my system without
any change in CPU.



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.