[chandler-users] Chandler experiences: Memory and performance issues

[Andre Mueninghoff]

Hi Peter,

I know what you mean about resource usage on WinXP. Yours sounds higher 
than mine. Once loaded, I see Chandler using about 100M of RAM. On 
shutdown, Chandler loads your repository into memory to check it, so, 
yes, there will be an increase in memory usage until it completes that 
task. I also have about 2,000 unique items in Chandler. It does take a 
bit of time to start, but I've found that for most operations it is 
fairly speedy. It also is probably true that I have become "acclimated" 
to Chandler's response times. It is still betaware after all. I will 
agree that sometimes at the most inopportune moment, Chandler will 
decide to chug on something and force me to wait. Fortunately, this does 
not happen all that often.

 From a data maintenance perspective, I have found that compacting my 
repository regularly, more often than the automatic compact every six 
days, speeds performance. Also, currently, Chandler stores multiple past 
versions of every item in its repository, very useful I think for 
troubleshooting, but it adds to the resource usage. Chandler does not 
copy the item version history to its export file. If you export your 
repository to a .chex (Chandler import/export file), and then reload 
that .chex file (which will result in a new repository database being 
created), you also will see a performance boost.

Good luck,
Andre

Peter Novak wrote:
> So I have a question: Is there anything I can do to make Chandler run
> faster on my computer except for buying a new one?