accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-3477) Evaluate use of TThreadedSelectorServer
Date Sun, 05 Apr 2015 05:21:33 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Elser updated ACCUMULO-3477:
---------------------------------
    Fix Version/s:     (was: 1.7.0)
                   1.8.0

> Evaluate use of TThreadedSelectorServer
> ---------------------------------------
>
>                 Key: ACCUMULO-3477
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3477
>             Project: Accumulo
>          Issue Type: New Feature
>          Components: master, tserver
>            Reporter: Josh Elser
>             Fix For: 1.8.0
>
>
> I re-read https://github.com/m1ch1/mapkeeper/wiki/Thrift-Java-Servers-Compared today,
specifically the section on thshaserver vs tthreadedselectorserver.
> {quote}
> TThreadedSelectorServer performs better than THsHaServer when the network io is the bottleneck
> {quote}
> This made me think that in read-heavy environments, we may benefit from using the TThreadedSelectorServer
instead of the THsHaServer. I know from previous experiments that we can spend a significant
amount of time for a query just sending bytes over the wire from server(s) to a client. Improving
this case may have benefit.
> Like THsHaServer, TThreadedSelectorServer relies on the TFramedTransport, so this is
only relevant for non-SSL and non-SASL cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message