Question: how to config memory with SolrPerformanceFactor

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Question: how to config memory with SolrPerformanceFactor

James liu-2
How to calc memory's size when i use solr.

i read
http://wiki.apache.org/solr/SolrPerformanceFactors#head-c4dfbdc1d256883e87f54cbb8160690d7997e4b3

but not know how to calc?

i find solr alway can work when i delete index,,i think it maybe cached in
memory.

is it just 'warm'?

and autowarmCount is the number which is warming documentCount?

if it is, how to calc it which cost memory size?

if it bigger than memory size which i config,,,,it will only store
autowarmCount document






--
regards
jl
Reply | Threaded
Open this post in threaded view
|

Re: Question: how to config memory with SolrPerformanceFactor

Mike Klaas
On 3/29/07, James liu <[hidden email]> wrote:

> i find solr alway can work when i delete index,,i think it maybe cached in
> memory.

Tricky, eh?  Unix doesn't _truly_ delete the files until all processes
have closed them or terminated.

-Mike
Reply | Threaded
Open this post in threaded view
|

Re: Question: how to config memory with SolrPerformanceFactor

James liu-2
ah,,,u means it will not truly deleted.

if we mv index.tmp$$ index,,,is it truly deleted?

if we notify solr open new searcher, solr just redirect to new index,,

Do old index cost memory size and hard disc space?

if it is not cached in memory,, does it means we no warry about OutOfMemory
when index file increase.

if it cached in memory, how to limit it? use autowarmCount?




2007/3/30, Mike Klaas <[hidden email]>:

>
> On 3/29/07, James liu <[hidden email]> wrote:
>
> > i find solr alway can work when i delete index,,i think it maybe cached
> in
> > memory.
>
> Tricky, eh?  Unix doesn't _truly_ delete the files until all processes
> have closed them or terminated.
>
> -Mike
>



--
regards
jl
Reply | Threaded
Open this post in threaded view
|

Re: Question: how to config memory with SolrPerformanceFactor

Chris Hostetter-3

: if we mv index.tmp$$ index,,,is it truly deleted?

it's not treuly deleted until no running processes have the file handles
open anymore.

: if we notify solr open new searcher, solr just redirect to new index,,

that will cause Solr to close the existing filehandles and open new ones,
so then the files will be deleted.

: Do old index cost memory size and hard disc space?

if they are open, then yes they cost memory -- they cost disk until truely
deleted.

: if it is not cached in memory,, does it means we no warry about OutOfMemory
: when index file increase.

i dont' understand your question.

: if it cached in memory, how to limit it? use autowarmCount?

autowarmCount is a solr cache option .. solr caches are for very specific
things -- they have no control over how much memory LUcene uses for the
bulk of your index.

changing an autowarnCount actually has very little to do with the amount
of total memory Solr uses -- the *size* of each of your caches is a much
more significant factor in how much ram is used by the process.



-Hoss

Reply | Threaded
Open this post in threaded view
|

Re: Question: how to config memory with SolrPerformanceFactor

James liu-2
Thk u Chris.

i just wanna know how to manage master and slaver hardware, for example ram
and disc 's  size.



2007/3/31, Chris Hostetter <[hidden email]>:

>
>
> : if we mv index.tmp$$ index,,,is it truly deleted?
>
> it's not treuly deleted until no running processes have the file handles
> open anymore.
>
> : if we notify solr open new searcher, solr just redirect to new index,,
>
> that will cause Solr to close the existing filehandles and open new ones,
> so then the files will be deleted.
>
> : Do old index cost memory size and hard disc space?
>
> if they are open, then yes they cost memory -- they cost disk until truely
> deleted.
>
> : if it is not cached in memory,, does it means we no warry about
> OutOfMemory
> : when index file increase.
>
> i dont' understand your question.
>
> : if it cached in memory, how to limit it? use autowarmCount?
>
> autowarmCount is a solr cache option .. solr caches are for very specific
> things -- they have no control over how much memory LUcene uses for the
> bulk of your index.
>
> changing an autowarnCount actually has very little to do with the amount
> of total memory Solr uses -- the *size* of each of your caches is a much
> more significant factor in how much ram is used by the process.
>
>
>
> -Hoss
>
>


--
regards
jl