Adam wrote:
I suspect that your performance problem is not related solely to hardware
specs. I recommend that you try creating a new workspace, with a new
connection. Then open one of the source members for which outline in
performing poorly, and try updating the outline. I suspect it will
preform well.
Creating a new workspace is not necessary to solve this problem. Creating
a new workspace is how I used to solve the problem. IBM came up with a
better way:
The developers want us to try to clear the cache, not the
iSeries - Program Verifier - Refresh Cache preference. I thought
that we tried this when you first called in but I don't have it
documented. If we can clear those out, then maybe you can just keep
using your existing (old?) workspace. And not have to get into how to
copy over all the settings between workspaces
Try clearing all the cache. From the Window menu,
select Preferences. Go to Remote Systems -> File Cache, and press the
Clear button. Also, in preferences, go to Remote Systems -> iSeries ->
Cache, and clear the cache.
Add to this: Then shut down and restart WDSC, to
also clear the cache objects residing in memory.
This procedure does work. I took a workspace which was showing this
problem, 12 minutes to verify a program for example and followed the
instructions. The initial verify afterwards was 2 minutes, to rebuild the
cache and then around 30 seconds for sequence verifies after the cache was
rebuilt. Outlining showed the same kind of improvement.
Bill Blalock
AGlauser@xxxxxxxxxxxx
07/12/2007 09:08 AM
Please respond to Websphere Development Studio Client for iSeries
To: Websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx>
cc: (bcc: Bill Blalock/TUS/US/Certegy)
Subject: Re: [WDSCI-L] Hardware requirements advise...
Robert A. Rogerson wrote on 12/07/2007 07:31:20:
I'm currently using WDSc 7.0 on a 2.66 GHz Pentium 4 with 1.74 GB of
Ram.
Basic editing works okay but if I try other functionality (such as
Outline
view refresh) the response is measured in minutes. I have been given
the go
ahead to purchase additional hardware to make this more workable.
I suspect that your performance problem is not related solely to hardware
specs. I recommend that you try creating a new workspace, with a new
connection. Then open one of the source members for which outline in
performing poorly, and try updating the outline. I suspect it will
preform well.
WDSC seems to still have some problems with the caching code (poor
performance when cache is full, for example), as well as with corrupting
workspaces. A corrupted workspace can cause all manner of problems.
Hope this helps,
Adam
Attention:
The information contained in this message and or attachments is
intended only for the person or entity to which it is addressed and may
contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this
information by persons or entities other than the intended recipient is
prohibited. If you received this message in error, please contact the
sender and
delete the material from any system and destroy any copies. Thank you for
your
time and consideration.
Attention:
Le contenu de ce message et(ou) les fichiers ci-joints s’adressent
exclusivement à la personne ou -entité à laquelle ils sont destinés. Ils
peuvent
contenir de l’information confidentielle, protégée et(ou) classifiée. Il
est
strictement interdit à toute personne ou entité autre que le(la)
destinataire
prévu(e) de ce message d’examiner, de réviser, de retransmettre ou de
diffuser
cette information, de prendre une quelconque action en fonction ou sur la
base
de celle-ci, ou d’en faire tout autre usage. Si vous avez reçu ce message
par
erreur, veuillez communiquer avec l’expéditeur(trice), supprimer ce
message et
les fichiers ci-inclus de tout système, et en détruire toutes copies,
qu’elles
soient électroniques ou imprimées. Nous vous remercions de votre entière
collaboration.
------------------------------------------------------------------------------
This message contains information from Certegy, Inc which may be confidential
and privileged. If you are not an intended recipient, please refrain from any
disclosure, copying, distribution or use of this information and note that such
actions are prohibited. If you have received this transmission in error,
please notify by e:mail postmaster@xxxxxxxxxxxx
==============================================================================
midrange.com
