[
https://issues.apache.org/jira/browse/SOLR-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679466#action_12679466
]
Mike Klaas commented on SOLR-1044:
----------------------------------
{quote} I haven't yet seen a HTTP server serving more than around 1200 req/sec
(apache HTTPD). A call based server can serve 4k-5k messages easily. (I am
yet to test hadoop RPC) . The proliferation of a large no: of frameworks around
that is a testimony to the superiority of that approach. {/quote}
up to 50,000 req/sec, with keepalive:
http://www.litespeedtech.com/web-server-performance-comparison-litespeed-2.0-vs.html
> Use Hadoop RPC for inter Solr communication
> -------------------------------------------
>
> Key: SOLR-1044
> URL: https://issues.apache.org/jira/browse/SOLR-1044
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Noble Paul
>
> Solr uses http for distributed search . We can make it a whole lot faster if
> we use an RPC mechanism which is more lightweight/efficient.
> Hadoop RPC looks like a good candidate for this.
> The implementation should just have one protocol. It should follow the Solr's
> idiom of making remote calls . A uri + params +[optional stream(s)] . The
> response can be a stream of bytes.
> To make this work we must make the SolrServer implementation pluggable in
> distributed search. Users should be able to choose between the current
> CommonshttpSolrServer, or a HadoopRpcSolrServer .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
