[CONTROLLER-901] Clustering : Improve performance of Shard#ReadDataReply message handling Created: 26/Sep/14 Updated: 03/Feb/15 Resolved: 03/Feb/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | Post-Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Abhishek Kumar | Assignee: | Kamal Rameshan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 2099 |
| Description |
|
Shard actor's message processing rate for ReadDataReply messages is just under 400ms (tested on my laptop). |
| Comments |
| Comment by Tom Pantelis [ 28/Oct/14 ] |
|
This should be improved by the NormalizedNode streaming work. |
| Comment by Tom Pantelis [ 03/Feb/15 ] |
|
This is no longer needed. NormalizedNode serialization has been improved with streaming and the ReadDataReply serialization is now done in the ShardReadTransaction actor to offload it from the Shard. |