Speed of opening in WDSc 5.0 was -> RE: Re: Re: Re: Opening a member without filters

I am wondering if there is the capability to run background jobs that don't
pose a performance threat to the active editor.  That would allow me to set
a preference somewhere stating this particular library/source file/member
should be re-cached every time I start WDSc.  I would put emphasis on this
not interfering with the initial time it takes me to get into WDSc nor
should it interfere with the speed of my current workspace.

Don't know if this is possible, just suggesting it. . .

Aaron Bartell

-----Original Message-----
From: Phil Coulthard [mailto:coulthar@xxxxxxxxxx]
Sent: Tuesday, May 27, 2003 3:47 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Re: Re: Re: Opening a member without filters


Paul, where was this article you read? George Farr and I have an article in
iSeries
mag in May, but if I recall we said WDSC has all of SEU's function. I don't
recall
us writing it is faster. Specifically, we said "is now competitive with, or
exceeds
SEU and PDM in terms of function". But maybe its another article you are
referring to.

Because we have to download data over a network, and convert from EBCDIC to
Unicode, the first edit will never be faster in WDSC than it is in SEU,
which merely
has to read it out of the database member and directly into a user space.
However,
by caching the member locally we are able to get close to SEU's performance
on
subsequent opens if it hasn't been changed by someone else in the meantime.
This is similar to adding it to a project, such that you are editing a
local copy. In this
case is only our parser that is overhead beyond what SEU has, which doesn't
color.

That being said, we are always experimenting to find different methods for
doing
the initial read and pulldown. We've tried jdbc and direct record access
via the
toolbox, and a couple other options. We will continue to look the best. For
example,
for those sites that have ftp turned on, we could allow you via preferences
to let us
use ftp for the transfer, which is the single faster known transfer
mechanism, I believe.

We also are constantly reviewing the parser code to look for opportunities
to squeeze
more performance out of it. We made strides in getting lists, transfering
files, and in
parsing files in the 5.0 release, and we will continue to work on the
performance of
all these in subsequent releases.  We do appreciate and need all feedback
as to
remaining problem areas so we can reproduce and flatten problems as best we
are able.

Phil Coulthard,  iSeries AD,  IBM Canada Ltd. coulthar@xxxxxxxxxxx

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.