Tuning Scarab

Run Scarab in production is very different then Scarab in test. Below are some tips.

Web Context Changes

Change the tomcat context tag so that reloadable=false. Or, alternatively, change it to true, but set the checkInterval to a larger number like 180.

TurbineResources Changes

You should change the TurbineResources.properties parameters so that velocity templates don't auto-reload. Set scarab.template.cache=TRUE to have caching turned on.

Tuning the cache

Scarab cache is central in the user experience of performance. You might want to take a look at the cache configuration file in: 

src/conf/classes/cache.ccf
There you can tweak the number of objects (MaxObjects) of every type that will be kept in memory.
  • Module: If your instance is known to be limitated to a given number of modules, this should get a similar range.
  • ScarabUser: Must be an aproximation to the maximum concurrent number of users.
  • Issue: A minimum equivalent to the ScarabUser's would be fine. Maybe something more, to keep a performance margin.

Keep in mind: The greatest the size of the cache, the better performance AND the greater memory needs.