The triangle algorithm optimizes the scenario where the originator is not the primary owner of key, by sending ordered update from the primary to the backup.

Current implementation orders the updates by segments and if 2 or more keys in the same segment are updated concurrently, they must be updated in the backup sequential by the same order (safety condition, keeps the data consistent).

This approach has a negative impact in the scenario where the originator is the primary owner. However, in server mode (more precise in hot rod protocol), the clients connect directly to the primary owner of a key. This leads to a performance degradation with the triangle.

Using the old algorithm only in server mode brings the performance back to normal.