[
https://issues.apache.org/jira/browse/SOLR-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028325#comment-14028325
]
Dmitry Kan commented on SOLR-3585:
----------------------------------
I would agree with [~dsmiley]. Every good api (and to some extent Solr is an
api in the client view) takes advantage of multi-threading by itself. In this
case a client can be as thin as possible and not care about threads. And if
client has enough idle cpus, sure, it could post in parallel. For example, we
run solr on pretty beefy machines with lots of cpu cores and most of the time
those are idling.
Some of the latest findings of ours with soft commits and high posting pressure
show, that posting may sometimes even fail and failed docs re-posting fixes the
issue.
> processing updates in multiple threads
> --------------------------------------
>
> Key: SOLR-3585
> URL: https://issues.apache.org/jira/browse/SOLR-3585
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 4.0-ALPHA, 5.0
> Reporter: Mikhail Khludnev
> Attachments: SOLR-3585.patch, SOLR-3585.patch, multithreadupd.patch,
> report.tar.gz
>
>
> Hello,
> I'd like to contribute update processor which forks many threads which
> concurrently process the stream of commands. It may be beneficial for users
> who streams many docs through single request.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
