Very helpful link. Thanks for sharing that.
-Deepak
On Wed, Sep 11, 2013 at 4:34 PM, Shawn Heisey wrote:
> On 9/11/2013 4:16 PM, Deepak Konidena wrote:
>
>> As far as RAM usage goes, I believe we set the heap size to about 40% of
>> the RAM and less than 10% is availa
of
the RAM and less than 10% is available for OS caching ( since replica takes
another 40%). Why does unallocated RAM help? How does it impact performance
under load?
-Deepak
On Wed, Sep 11, 2013 at 2:50 PM, Shawn Heisey wrote:
> On 9/11/2013 2:57 PM, Deepak Konidena wrote:
>
>> I
ey - Could you elaborate more about the "broker" core and
delegating the requests to other cores?
-Deepak
On Wed, Sep 11, 2013 at 1:10 PM, Shawn Heisey wrote:
> On 9/11/2013 1:07 PM, Deepak Konidena wrote:
>
>> Are you suggesting a multi-core setup, where all the cores s
you a performance benefit.
>
> I've certainly heard of that done at Amazon, with a separate EBS volume
> per core giving some performance improvement.
>
> Upayavira
>
> On Wed, Sep 11, 2013, at 07:35 PM, Deepak Konidena wrote:
> > Hi,
> >
> > I know that S
3 at 12:11 PM, Greg Walters wrote:
> Why not use some form of RAID for your index store? You'd get the
> performance benefit of multiple disks without the complexity of managing
> them via solr.
>
> Thanks,
> Greg
>
>
>
> -Original Message-
> Fr
Hi,
I know that SolrCloud allows you to have multiple shards on different
machines (or a single machine). But it requires a zookeeper installation
for doing things like leader election, leader availability, etc
While SolrCloud may be the ideal solution for my usecase eventually, I'd
like to know
Does the order of fields matter in a lucene query?
For instance,
q = A && B && C
Lets say A appears in a million documents, B in 1, C in 1000.
while the results would be identical irrespective of the order in which you
AND
A, B and C, will the response times of the following queries differ
One of my previous mails to the group helped me simulate short-circuiting
OR behavior using (thanks to yonik)
_val_:"def(query(cond1,cond2,..))"
where if cond1 is true the query returns without executing the subsequent
conditions.
While it works successfully for single attribute, I am trying to
I understand that lucene's AND (&&), OR (||) and NOT (!) operators are
shorthands for REQUIRED, OPTIONAL and EXCLUDE respectively, which is why
one can't treat them as boolean operators (adhering to boolean algebra).
I have been trying to construct a simple OR expression, as follows
q = +(field1:
