-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
The goal is to (a) reduce the number of properties needed and (b) determine the values dynamically.
Examples:
- Determine the best min/max size of a thread pool
- Find out what the best timeout values are for retransmission, e.g. based on average retransmission times
- Determine the optimal number of credits in FC
This is similar to the JVM setting where, starting with 1.5, the initial values can be set, but over time, the JVM dynamically changes them.
In the best case, a config contains only a list of protocols without any properties, and JGroups will figure out the correct values.
- is related to
-
JGRP-1037 Ergonomics: size thread pools dynamically
- Resolved
-
JGRP-1118 NAKACK: use_mcast_xmit should be set based on the available transport
- Resolved
-
JGRP-1053 UNICAST: set retransmission timeout based on actual retransmission times
- Open
-
JGRP-1054 NAKACK: retransmission timeouts based on actual retransmission values
- Open
- relates to
-
JGRP-1129 Ergonomics: size max_bundle_size and max_bundle_timeout (in TP) dynamically
- Resolved
-
JGRP-1238 STABLE: determine best value for max_bytes
- Resolved
-
JGRP-1244 Discovery: set max_rank dynamically
- Resolved