On Fri, Feb 16, 2007 at 11:25:38AM +0000, Alan Burlison wrote: > Will Fiveash wrote: > > >BTW, if I had know the insane about of mods I would end up making to wx > >I would have recoded the whole thing in perl. Something to think about. > > +1 > > I'd dearly like to see the core functionality pulled into a reusable > library so that other tools (e.g. the gatekeeper ones) could reuse the > same bits. Plus wx is horribly inefficient, it's pretty useless on > really large workspaces.
I agree that wx has perf. issues but I will point out three things that can really speed up wx performance when tracking a lot of workspace change: 1. Don't let wx auto sort the active list. Sorting can be done at any point in time via 'wx update -q -s'. 2. The parent workspace should be as close as possible to the local workspace. wx and the underlying Teamware commands access the parent frequently for some wx commands. To this end I usually make a local copy of the parent I'm working against. To make a fast copy I use: /net/tweedle-dum.central/export/home09/willf/bin/clone_ws. Note, this also speeds up wx webrev quite a bit as well. 3. If doing a thorough wx update (which I don't do normally since I use wx to make workspace changes) set PUTBACK environment variable to "cm_env -g -o putback" so Casper's turbo def.dir.flp is used to speed up the putback -n that wx is using. Oh and 4. use a really fast system. 8^) Note that I'm not defending wx, just want to provide some workarounds in case people are having problems in this regard. -- Will Fiveash Sun Microsystems Inc. Austin, TX, USA (TZ=CST6CDT) _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
