[CONTROLLER-1951] Eliminate TransactionContext.executeModification() Created: 25/Jun/20  Updated: 26/Jun/20  Resolved: 26/Jun/20

Status: Resolved
Project: controller
Component/s: clustering
Affects Version/s: None
Fix Version/s: Magnesium SR2, Sodium SR4, 2.0.3

Type: Improvement Priority: High
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to CONTROLLER-1950 CDS frontend incorrectly handles root... Resolved

 Description   

Refactor done in CONTROLLER-1950 makes it obvious that the internal interface between local, noop and remote contexts is needlessly allocating AbstractModifications.

Without the refactor, this actually hurts, because we are performing two allocations, which actually may not be properly escape-analyzed.

After the refactor the allocation short-lived, so can be inferred out in local case dominance – but it also means TransactionProxy knows about remoting objects. It clearly should not, as those objects should be allocated only in RemoteTransactionContext.


Generated at Wed Feb 07 19:56:50 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.