Compare, selecting Update eDir or Designer performance issue

Designer 3.0 M3 (20080404) build.

Is this just me, or is anyone else seeing this performance issue?

I do a compare, it takes time (about 3-4 minutes but I have on the order 
of 30+ busy drivers, so I actually think the compare is pretty quick), 
then I get my summary window.

Jumping from driver to driver, item to item is quick.  Selecting an item 
and looking at the differences is quick.  Snappy as a UI should be.

But as soon as I select Update eDirectory or Update Designer, I get a 
7-10 seconds delay before the fancy new directional arrow shows up.

It does not seem to be specific to a particular driver, (i.e. All the 
drivers I look at in a compare are slow in this aspect) nor does it seem 
to be item specific.  I.e. XMLData versus Deploy the whole object, 
versus a GCV value.

On Tue, 13 May 2008 14:04:09 GMT, Geoffrey Carman
<geoffreycarman@gmail.com> wrote:

>Is this just me, or is anyone else seeing this performance issue?

Not this one, no. I think I'm seeing the general slowdown you were
talking about, though. I've been busy in Designer today (5 new drivers
developped, deployed, and being tested now). The longer I have Designer
running, and the more I do with it, the higher the memory used indicator
goes, and the slower it's getting.


---------------------------------------------------------------------------
 David Gersic                                            dgersic_@_niu.edu
 Novell Support Forums Volunteer SysOp            http://forums.novell.com

David Gersic wrote:
> On Tue, 13 May 2008 14:04:09 GMT, Geoffrey Carman
> <geoffreycarman@gmail.com> wrote:
> 
>> Is this just me, or is anyone else seeing this performance issue?
> 
> Not this one, no. I think I'm seeing the general slowdown you were
> talking about, though. I've been busy in Designer today (5 new drivers
> developped, deployed, and being tested now). The longer I have Designer
> running, and the more I do with it, the higher the memory used indicator
> goes, and the slower it's getting.

What I find is that quitting and starting again does not make it go any 
faster though.  I too suspected RAM/stuff in memory, but I don't think so.

Brady looked at my project I sent him and says part of it looks 

On Wed, 14 May 2008 19:04:40 GMT, Geoffrey Carman
<geoffreycarman@gmail.com> wrote:

>> Not this one, no. I think I'm seeing the general slowdown you were
>> talking about, though. I've been busy in Designer today (5 new drivers
>> developped, deployed, and being tested now). The longer I have
Designer
>> running, and the more I do with it, the higher the memory used
indicator
>> goes, and the slower it's getting.
>
>What I find is that quitting and starting again does not make it go any 
>faster though.  I too suspected RAM/stuff in memory, but I don't think so.

Hm, ok, different issue then. Mine got really slow (20+ minutes to open
a policy). Exit and restart Designer and it went back to normal.


---------------------------------------------------------------------------
 David Gersic                                            dgersic_@_niu.edu
 Novell Support Forums Volunteer SysOp            http://forums.novell.com