Re: [Statcvs-users] Latest CVS-Checkout of statcvs terribly slow

[Richard C. <ri...@cy...>]

Hi Wolfgang,

From: "Pedot, Wolfgang" <wp...@ha...>
> [...] I noticed that the new build is awfully slow.

For small repositories, the current build is *a bit* slower because of
additional charts, and requires *much* more memory because we use a
different collection class (tree-based instead of array-based).

The larger memory footprint turns into a heavy performance hit when the JVM
has to garbace collect all the time or starts swapping. I guess that's
what's happening in your case.

So here's what you can do (not very useful, I know ...):

- buy more RAM

- fiddle with the -mx setting to set the max amount of RAM for the JVM:
  "java -mx512m -jar statcvs.jar ..."

- use the -verbose switch of StatCvs to see if it's still running and
  how much memory it needs (shown after finishing)

Richard