: I won't have access to the code until monday, but i'm pretty sure this
: should be a fairly trivial change (just un-set the estimator on the
: CacheEntry objects)
done, see notes in SOLR-1292
-Hoss
: > we can always turn the size estimator off ... or turn it only only when
: > doing the insanity checks (so normal stats are fast, buf if anything is
: > duplicated you'll get info on the size of the discrepancy)
:
: Is this something we want to do before release? I'm not at all
: familiar wit
On Tue, Oct 6, 2009 at 5:51 PM, Chris Hostetter
wrote:
>
> : When I was working on it, I was actually going to default to not show
> : the size, and make you click a link that added a param to get the sizes
> : in the display too. But I foolishly didn't bring it up when Hoss made my
> : life easie
: When I was working on it, I was actually going to default to not show
: the size, and make you click a link that added a param to get the sizes
: in the display too. But I foolishly didn't bring it up when Hoss made my
: life easier with his simpler patch.
we can always turn the size estimator
thx much guys, no biggie for me, i just wanted to get to the bottom of
it in case i had screwed something else up..
--joe
On Tue, Oct 6, 2009 at 1:19 PM, Mark Miller wrote:
> I was worried about that actually. I havn't tested how fast the RAM
> estimator is on huge String FieldCaches - it will b
I was worried about that actually. I havn't tested how fast the RAM
estimator is on huge String FieldCaches - it will be fast on everything
else, but it checks the size of each String in the array.
When I was working on it, I was actually going to default to not show
the size, and make you click a
Might be the new Lucene fieldCache stats stuff that was recently added?
-Yonik
http://www.lucidimagination.com
On Tue, Oct 6, 2009 at 3:56 PM, Joe Calderon wrote:
> hello *, ive been noticing that /admin/stats.jsp is really slow in the
> recent builds, has anyone else encountered this?
>
>
> --
hello *, ive been noticing that /admin/stats.jsp is really slow in the
recent builds, has anyone else encountered this?
--joe
