Re: WDSC lockup (was: Rational Updater)

We seem to have a disconnect here.  I understand what you're trying to
communicate, but you apparently think I'm trying to write that WDSC will
lock up any PC.  You'll note that I never wrote that.  The point was and
is that RSE blocks the UI thread.  On my previous PC, this had
worse-than-usual consequences.  These consequences may have been
localized to my PC, but that doesn't change the fact that blocking in
the UI thread is bad design.


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Joe Pluta
Sent: Sunday, March 05, 2006 2:21 PM
To: 'Websphere Development Studio Client for iSeries'
Subject: Re: [WDSCI-L] WDSC lockup (was: Rational Updater)

Again, never happened to me in all the time I've been using the product.
I've run WDSC on a PC with <2GHz processor and under 1GB of RAM and
never
saw that happen.  My laptop is considerably less powerful than that.
WDSC
locked up, which meant that I couldn't do anything else in the
workbench,
but I could still access other applications such as Windows Explorer or
Word.

Joe

> From: Dean, Robert
> 
> I didn't say it locked up hard.  This happened on my old PC, and was
one
> of the reasons I got a new PC.  I was researching the effects various
> source member partitioning schemes would have on RSE filter
performance.
> The extreme case -- return all 20,000+ source members from a single
> source file -- locked up my PC for 15 minutes while it was processing
> (Windows wouldn't respond to mouse clicks, Ctrl-Shift-Esc or Alt-Tab).
> Other filter strategies that returned 5,000 - 7,000 results locked it
up
> for 5 minutes.
> 
> Old PC configuration
> Pentium 4 2.6 GHz (not a hyperthreading model)
> 2GB PC2100 RAM
> Plenty of free HD space
> 1600x1200x32 resolution in Intel chipset
> WDSC 6.0 (RAD 6.0.1, WAS 6.0.2.5, WDSC 6.0.0.3)