[
https://issues.apache.org/jira/browse/CASSANDRA-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-1911.
---------------------------------------
Resolution: Won't Fix
Assignee: (was: Jonathan Ellis)
there are (potentially) multiple messages per write; creating more garbage to
track those in StorageProxy.mutate is going to eat up what little performance
advantage this would create, in addition to adding complexity.
> write path should call MessagingService.removeRegisteredCallback
> ----------------------------------------------------------------
>
> Key: CASSANDRA-1911
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1911
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7.1
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> it would reduce memory overhead to pre-emptively clear the callback when done
> the way the read path does.
> (other IAsyncCallbacks could do this too, but only read/write have enough
> volume to matter.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
