lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <erickerick...@gmail.com>
Subject Re: Limitation on number of cores a solr instance can handle
Date Tue, 14 Jun 2011 00:56:38 GMT
No, there's no a-priori limit to the number of cores Solr
can handle, most generally you run into issues
with machine memory (and its effect on performance) that
requires you to split the cores amongst separate machines
eventually. Only testing will tell you that point for your app.

Unfortunately, it's impossible to say "how many cores is
too many" generally, too much depends upon the particular
characteristics of your application. How much are you
sorting? Faceting? Etc. etc. etc. Gotta test...

Best
Erick

On Mon, Jun 13, 2011 at 4:51 PM, Bin Lan <binlan@perimeterusa.com> wrote:
> Dear All,
>
> We are currently learning solr, and have some questions on multicore
> setting.
>
> First, is there a limitation on number of cores a solr instance can handle?
> From what I can tell, a core is basically a entry in a Map, so there should
> (virtually) not be any limits on how many cores one could deployed in a
> single solr instance.
>
> Second, would large number of cores affect solr's performance? We are
> currently using plain old lucene as our searching library. And we have not
> too much trouble to separated our indexes according to different properties,
> e.g. each client has its own index. I am wondering if anyone has done a
> similar setting and partitioning their indexes to many small individual
> ones. And how is the performance?
>
> Thank you.
>
> Regards
> -
> Bin Lan
> Software Engineer
> Perimeter E-Security
> O - (203)541-3412
>
> Follow Us on Twitter: www.twitter.com/PerimeterNews
> Read Our Blog: security.perimeterusa.com/blog
>
>
>
>
> --
>  The sender of this email subscribes to Perimeter E-Security's email
>  anti-virus service. This email has been scanned for malicious code and is
>  believed to be virus free. For more information on email security please
>  visit: http://www.perimeterusa.com/services/messaging
>  This communication is confidential, intended only for the named recipient(s)
>  above and may contain trade secrets or other information that is exempt from
>  disclosure under applicable law. Any use, dissemination, distribution or
>  copying of this communication by anyone other than the named recipient(s) is
>  strictly prohibited. If you have received this communication in error, please
>  delete the email and immediately notify our Command Center at 203-541-3444.
>
>  Thanks --20cf3071ca623be36c04a59e17c2
> Content-Type: text/html; charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
>
> Dear All,<br><br>We are currently learning solr, and have some questions
on=
>  multicore setting. <br><br>First, is there a limitation on number of cores=
>  a solr instance can handle? From what I can tell, a core is basically a en=
> try in a Map, so there should  (virtually) not be any limits on how many co=
> res one could deployed in a single solr instance.<br>
>
> <br>Second, would large number of cores affect solr&#39;s performance? We a=
> re currently using plain old lucene as our searching library. And we have n=
> ot too much trouble to separated our indexes according to different propert=
> ies, e.g. each client has its own index. I am wondering if anyone has done =
> a similar setting and partitioning their indexes to many small individual o=
> nes. And how is the performance?=C2=A0 <br>
>
> <br>Thank you.<br clear=3D"all"><br>Regards<br>-<br>Bin
Lan<br>Software Eng=
> ineer<br>Perimeter E-Security<br>O - (203)541-3412<br><br>Follow
Us on Twit=
> ter: <a href=3D"http://www.twitter.com/PerimeterNews" target=3D"_blank">www=
> .twitter.com/PerimeterNews</a><br>
>
> Read Our Blog: <a href=3D"http://security.perimeterusa.com/blog" target=3D"=
> _blank">security.perimeterusa.com/blog</a><br><img src=3D"http://www.perime=
> terusa.com/public/images/header-logo-perimeter.gif"><br><br>
>

Mime
View raw message