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



I didn't think about that...I am on a big machine now:-)

2 Xeon dual core procs.
4GB RAM
400GB mirrored SATA HD's (only 7200RPM, wish I had 10000RPM)

I always thought Verify was slow because it had to go to the server to
download /copy books and PF layouts. Guess if I have done a refresh in the
Outline view it has all that available.

Aaron Bartell
http://mowyourlawn.com



-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of smorrison@xxxxxxxxxxxxxxxxxxx
Sent: Wednesday, May 09, 2007 8:24 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Verify is crazy fast!

Have you changed PCs, Aaron? That's when I saw a major improvement in the
speed of Verify. Using WDSCi V6 on my old PC, Verify took 30 seconds, while
Compile took about 5 seconds. When my PC got upgraded, Verify only took
about 5 seconds, about the same as a compile. The new PC is a Dell Optiplex
740, dual core AMD processor with 2GB RAM and high performance drive. (That
thing rattles when the heads are seeking.) With WDSCi V7, both the compile
and verify are less than 3 seconds. I think the biggest performance
improvement is the RAM increase. I tried to get more RAM on my old PC, but
instead of upgrading that, they moved up the replacement of my old PC to
pass it on to someone else here.

Steve


Steven Morrison
Fidelity Express
903-885-1283 ext. 479


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.