Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
-
Normal
-
Docs
Description
The default in 2.2+ was to enable TIMEHORIZON message coalescing. After reports of performance regressions after upgrading from 2.1 to 2.2/3.0 we have discovered the issue to be this default.
We need to re-test our assumptions on this feature but in the meantime we should default back to disabled.
Here is a performance run with and without message coalescing