[
https://issues.apache.org/jira/browse/CASSANDRA-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661645#comment-13661645
]
Vijay edited comment on CASSANDRA-5582 at 5/19/13 8:47 PM:
-----------------------------------------------------------
Hi Pavel and All,
I should say this patch is Awesome!
Overall i saw "> 30%" improvement at-least for most cases. The tests where done
with 32 Core Intel 128GB and SSD Drives.
For 4 Nodes i was able to do 100K Reads Per Sec with this patch, before (trunk)
it was less than 50K.
But i have to say it exposes other issues in the Storage Proxy layer... For
example i was noticing write failing silently without hints been stored etc.
was (Author: [email protected]):
Hi Pavel and All,
I should say this patch is Awesome!
Overall i saw "> 30%" improvement for most cases. The tests where done with 32
Core Intel 128GB and SSD Drives.
For 4 Nodes i was able to do 100K Reads Per Sec with this patch before it was
less than 50K.
But i have to say it exposes other issues in the Storage Proxy layer... For
example i was noticing write failing silently without hints been stored etc.
> Replace CustomHsHaServer with better oprtimized solution based on LMAX
> Disruptor.
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-5582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5582
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Pavel Yaskevich
> Assignee: Pavel Yaskevich
> Fix For: 2.0
>
> Attachments: CASSANDRA-5582.patch, disruptor-3.0.0.beta3.jar,
> disruptor-thrift-0.1-SNAPSHOT.jar, Pavel's Patch.rtf
>
>
> I have been working on https://github.com/xedin/disruptor_thrift_server and
> consider it as stable and performant enough for integration with Cassandra.
> Proposed replacement can work in both on/off Heap modes (depending if JNA is
> available) and doesn't blindly reallocate things, which allows to resolve
> CASSANDRA-4265 as "Won't Fix".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
