te, yes. But there
> could be a potentially substantial delay between a commit message being sent
> and the new documents actually searchable.
>
> Erik
>
---
Antonio Lobato
Symplicity Corporation
www.symplicity.com
(703) 351-0200 x 8101
alob...@symplicity.com
in command line. I had tried to
> force GC collection via Jconsole at the end of the run but it didn't
> seems to do anything the heap size.
> -Yao
>
> -Original Message-
> From: Antonio Lobato [mailto:alob...@symplicity.com]
> Sent: Monday, May 17,
faceting-and-memory-leaks-tp824372p824372.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
---
Antonio Lobato
Symplicity Corporation
www.symplicity.com
(703) 351-0200 x 8101
alob...@symplicity.com
in a few
seconds.
Actually, I would not drop these cache numbers. With a cache of 30k
documents we had a hitraion of 60%, decreasing this size the hitratio
decreased as well. With a hitratio of currently 30% it seems to be
better to disable caching anyway. Of course we would love to use caching
;-
Drop those cache numbers. Way down. I warm up 30 million documents in about 2
minutes with the following configuration:
Mind you, I also use Solr 1.4. Also, setup a decent warming query or two, as
so:
date:[NOW-2DAYS TO NOW] 0
100 date desc
Don't warm fa
I've actually run into this issue; huge, 30 minute warm up times. I've
found that reducing the auto-warm count on caches (and the general size
of the cache) helped a -lot-, as did making sure my warm up query wasn't
something like:
q=*:*&facet=true&facet.field=somethingWithAWholeLotOfTerms
T
Hey everyone, I don't actually have a question, but I just thought I'd
share something really cool that I did with Solr for our company.
We run a good amount of servers, well into the several hundreds, and
naturally we need a way to centralize all of the system logs. For a
while we used a com
ut if you search the user list for memory, you'll see this
kind of thing discussed a bunch of times, along with
suggestions for tracking it down, whether it's just
postponed GCing, etc.
HTH
Erick
On Mon, Jan 25, 2010 at 10:47 AM, Antonio Lobato >wrote:
Hello everyone!
I have a
Hello everyone!
I have a question about indexing a large dataset in Solr and ram
usage. I am currently indexing about 160 gigabytes of data to a
dedicated indexing server. The data is constantly being fed to Solr,
24/7. The index grows as I prune away old data that is not needed, so
th
