I would also add:
* Lock acquisition timeout
* various thread pool sizes
Cheers
Manik
On 21 Jul 2011, at 20:20, Paolo Romano wrote:
Hi,
in the last Cloud-TM's meeting in Rome we have discussed the idea of
posting a poll asking to ISPN's users which parameters they consider
more complex to tune, or which parameters they consider as more
important to be self-tuned.
Before we post the poll, however, we thought to first ask you if you
think that we could suggest also different parameters.
The current list of parameters includes:
- size of the marshalling buffer
- frequency with which replicationQueue (for asynchronous acks) is
processed:
- clustering->async-> replQueueMaxElements
- clustering->async-> replQueueInterval
-number of max concurrent transactions (currently this is
unbounded, but we could self-tune the multi-programming level to
maximize performance depending on the number of available cores, the
actual conflict rate among transactions etc.)
-lock striping, also adapting size of lock pool (striping can lead
to false sharing, but reduce the memory footprint and the size of the
exchanged messages)
-adaptive timeout for deadlock detection, based on the avg duration
of a transaction/conflict rate etc
Any suggestions?
Cheers,
Paolo
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev