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



UPDATE:
Is Refresh Cache Off at the Preferences level or just the Verify command
level? If you have Cache off at the Preferences level and do NOT override
it
at Verify with Prompt, you should be OK. If you have Cache on at the
Preferences level and do not use Verify with Prompt, it will refresh each
time. This can be overridden at the Verify w/ prompt command.




MKirkpatrick@xxxxxxxxxxxxxxxxx
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
05/01/2007 12:00 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] verify performance






Is Refresh Cache Off at the Preferences level or just the Verify command
level? If you have Cache off at the Preferences level and do override it
at Verify with Prompt, you should be OK. If you have Cache on at the
Preferences level and do not use Verify with Prompt, it will refresh each
time. This can be overridden at the Verify w/ prompt command.

Michael Kirkpatrick
Western Dental Services, Inc.
Information Systems
(
Phone:
(714) 571.3582
(
Toll free:
(800) 471.4444
7
Fax:
(714) 480.3001
*
Email:
mkirkpatrick@xxxxxxxxxxxxxxxxx
8
Web:
http://www.westerndental.com/





Dave Shaw <daveshaw@xxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
05/01/2007 11:49 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
<wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] verify performance






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.

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.