verify performance -- WDSCI-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: verify performance
From: Dave Shaw <daveshaw@xxxxxxxxxxxxx>
Date: Tue, 1 May 2007 13:49:12 -0500
List-archive: <http://archive.midrange.com/wdsci-l>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Websphere Development Studio Client for iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

I'm getting frustrated with slow verifies (and outline refreshes) in WDSCi
7.0.0.1. Is there anything I can do to improve performance? I have cache on,
refresh cache off, and I'm most concerned about instances where I've already
run a verify once so that the cache should be loaded. Verifies almost always
run MUCH longer than in CODE, so I don't think it's due to our network.

Most blatant example today:

I had a verify on a display file take more than 5 minutes; the same verify in
CODE took less than 5 seconds.

Do I have something set wrong? If so, what should I look for?

Thanks.

Dave Shaw
Mohawk Industries

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: verify performance , MKirkpatrick
Re: verify performance , Violaine Batthish

This mailing list archive is Copyright 1997-2026 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.