Sizing Recommendation
Depending of the size of the events in a channel or queue, the value of Events Per Spindle should be adjusted properly. A smaller setting for Events Per Spindle is recommended for big events and a bigger setting for Events Per Spindle is recommended for small events.
As a general guideline, we suggest you use a spindle size no bigger than 1GB, and ensure that number of events stored per spindle is at least 1000. If the spindle files are too big, this can affect disk usage. Similarly, if the spindle files are too small, this can affect read/write performance.
Examples
Here are some examples for recommended values of events per spindle, based on event size:
small events (<1KB per event): 100 000 events per spindle.
medium events (>= 1KB and < 20KB per event): 50 000 events per spindle. This is the default value.
large events (>= 20KB and =< 100KB per event): 10 000 events per spindle.
very large events (>= 1MB per event): 1000 events per spindle (though you need to consider that 1000 events at 1MB each are going to require 1GB on disk).
The above values are just recommendations and using values different from the above will not break the system.
Note:
To override the default value of Events Per Spindle (currently 50 000), the following system Java property can be set on the client side:
com.softwareag.um.client.store.EventPerSpindle