Here are the memory parameters I'm using now(Tomcat): -Xms2024m -Xmx2024m
With those values, the second query is way faster. Only the first one is
very slow.
Thanks for the tip.
However, I'm wondering if will be enough and I will not hit the same
issues when I will have many users searching at
Hi everybody,
I would like you to help me a bit about managing this multi-language part,
actually an example would be excellent.
So I did multi index in one core and I would like you to let me know what
you think about the way that I've managed that, is there more parameter that
I don't know, som
Jeremy,
Great troubleshooting! You were spot on.
I've posted a new patch that fixes the issue.
Erik
On Oct 16, 2008, at 9:53 PM, Jeremy Hinegardner wrote:
After a bit more investigating, it appears that any facet tree where
the first
item is numerical or boolean or some non-textua
Erik,
Thanks, its working great. Next is to make it distributed. I was thinking of
working on this, is the FacetCompoent a good model to work from to make the
TreeFacet distributed? I should probably join solr-dev for that conversation I
assume :-).
-jeremy
On Thu, Oct 16, 2008 at 11:12:45PM
You need to setup a warming query that sorts so that the initial long
query is done behind the scenes. Users first query will then be fast.
Solrconfig.
- Mark
On Oct 18, 2008, at 1:34 AM, christophe <[EMAIL PROTECTED]>
wrote:
Here are the memory parameters I'm using now(Tomcat): -Xms202
