Community Suggestion

I have a suggestion...  Could those of us who use this seriously 
consider donating some stupidly complex rules we have in production to 
the Designer team to use as a test case?

I.e. Lets design a Designer torture case...

I know I have submitted projects that have rules that trigger fun memory 
bugs.  (Nested-if's way deep nested seemed to leak memory, now fixed).

I have some display ones that are killing me...

I have some performance ones, where adding a new entry at the beginning 
of the rule is taking 20-30 seconds...

I was thinking come up with our worst case performance rule sets.  Give 
it to the Designer team to use when testing performance against real 
world data sets.

We would need someone from the Designer group to collect, collate and 

On Mon, 12 May 2008 18:28:34 GMT, Geoffrey Carman
<geoffreycarman@gmail.com> wrote:

>I.e. Lets design a Designer torture case...

I think it may be fairly said that you're *already* the Designer torture
case, Geoffrey.


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

On Mon, 12 May 2008 18:28:34 GMT, Geoffrey Carman wrote:

> Nested-if's way deep nested seemed to leak memory, now fixed

Hi Geoffrey,

What version are you using? I'm using 2.1.1 and kind of got used to the
slowness with very large rules (where iManager is a real speedy
navigating/editing the same rules...)

With large rules, I workaround the slowness by goind directly to the XML
Source view and work there... no fancy screen to draw, no time to wait.

I second your initiative, btw.
-- 

David Gersic wrote:
> On Mon, 12 May 2008 18:28:34 GMT, Geoffrey Carman
> <geoffreycarman@gmail.com> wrote:
> 
>> I.e. Lets design a Designer torture case...
> 
> I think it may be fairly said that you're *already* the Designer torture
> case, Geoffrey.

Ironically, I had you and Jeff specifically in mind for this posting. 
:)  I feel like one of is the kettle, the other is the pot...

Actually it my boss Rob who is the true master of Designer sadism.  I 
just follow in his footsteps!  :)  Alas, (for the Designer teams sake) I 
appear to be learning alot from his example!

I do figure that if we each contribute our worst performant rule set to 
the Designer group, and they use to base their performance testing, we 

Ofer Gigi wrote:
> On Mon, 12 May 2008 18:28:34 GMT, Geoffrey Carman wrote:
> 
>> Nested-if's way deep nested seemed to leak memory, now fixed
> 
> Hi Geoffrey,
> 
> What version are you using? I'm using 2.1.1 and kind of got used to the
> slowness with very large rules (where iManager is a real speedy
> navigating/editing the same rules...)
> 
> With large rules, I workaround the slowness by goind directly to the XML
> Source view and work there... no fancy screen to draw, no time to wait.

Well that is basically where I get left too at times.  For simple stuff 
that I need to pop up 6 windows to get to, I just edit XML.

For multi rule copy/paste, I just edit XML.   But it is nice having 
Policy Builder when writing the rules.  (I.e. I still do not recall the