|
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
As an Amazon Associate we earn from qualifying purchases.
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.