On 3/11/2014 11:05 AM, abhishek jain wrote:
hi Shawn,
Thanks for the reply,
Is there a way to optimize RAM or does Solr does automatically. I have
multiple shards and i know i will be querying only 30% of shards most of
time! and i have 6 slaves. so dedicating more slave with 30% most used
shar
hi Shawn,
Thanks for the reply,
Is there a way to optimize RAM or does Solr does automatically. I have
multiple shards and i know i will be querying only 30% of shards most of
time! and i have 6 slaves. so dedicating more slave with 30% most used
shards .
Another question:
Is it advised to serve
On 3/11/2014 6:14 AM, abhishek.netj...@gmail.com wrote:
> Hi all,
> What should be the ideal RAM index size ratio.
>
> please reply I expect index to be of size of 60 gb and I dont store contents.
Ideally, your total system RAM will be equal to the size of all your
program's heap requirements, p
Subject: Re: Optimizing RAM
Hi,
If I go with copy field than will it increase I/O load considering I have RAM
less than one third of total index size?
Thanks
Abhishek
Original Message
From: Erick Erickson
Sent: Monday, 10 March 2014 01:37
To: solr-user@lucene.apache.org
Reply To: solr-user
On Sun, 2014-03-09 at 19:55 +0100, abhishek jain wrote:
> I am confused should i keep two separate indexes or keep one index with two
> versions or column , i mean col1_stemmed and col2_unstemmed.
1 index with stemmed & unstemmed will be markedly smaller than 2 indexes
(one with stemmed, one with
: Re: Optimizing RAM
I'd go for a copyField, keep the stemmed and unstemmed
version in the same index.
An alternative (and I think there's a JIRA for this if not an
outright patch) is implement a "special" filter that, say, puts
the original tken in with a special character, s
I'd go for a copyField, keep the stemmed and unstemmed
version in the same index.
An alternative (and I think there's a JIRA for this if not an
outright patch) is implement a "special" filter that, say, puts
the original tken in with a special character, say $ at the
end, i.e. if indexing "running