I recently noticed the same sort of thing. The attached screenshot shows the transition on a search server when we updated from a Solr 1.4 dev build (revision 779609 from 2009-05-28) to the Solr 1.4.0 released code. Every 3 hours we have a cron task to log some of the data from the stats.jsp page from each core (about 100 cores, most of which are small indexes).
You can see there is a dramatic spiking of the load after the update - I think due to added reporting on that page such as from the lucene field cache. Is this amount of load expected? -Peter On Thu, Dec 24, 2009 at 12:23 PM, Jay Hill <jayallenh...@gmail.com> wrote: > Also, what is your heap size and the amount of RAM on the machine? > > I've also noticed that, when watching memory usage through JConsole or > YourKit while loading the stats page, the memory usage spikes dramatically - > are you seeing this as well? > > -Jay > > On Thu, Dec 24, 2009 at 9:12 AM, Jay Hill <jayallenh...@gmail.com> wrote: > >> I've noticed this as well, usually when working with a large field cache. I >> haven't done in-depth analysis of this yet, but it seems like when the stats >> page is trying to pull data from a large field cache it takes quite a long >> time. >> >> Are you doing a lot of sorting? If so, what are the field types of the >> fields you're sorting on? How large is the index both in document count and >> file size? >> >> Another approach to get data from the Solr instance would be to use JMX. >> And I've been working on a request handler (started by Erik Hatcher) that >> will provide the same information as the stats page, but a little more >> efficiently. I may try to put up a patch with this soon. >> >> -Jay >> >> >> >> On Wed, Dec 23, 2009 at 6:43 AM, Stephen Weiss <swe...@stylesight.com>wrote: >> >>> We've been using Solr 1.4 for a few days now and one slight downside we've >>> noticed is the stats page comes up very slowly for some reason - sometimes >>> more than 10 seconds. We call this programmatically to retrieve the last >>> commit date so that we can keep users from committing too frequently. This >>> means some of our administration pages are now taking a long time to load. >>> Is there anything we should be doing to ensure that this page comes up >>> quickly? I see some notes on this back in October but it looks like that >>> update should already be applied by now. Or, better yet, is there now a >>> better way to just retrieve the last commit date from Solr without pulling >>> all of the statistics? >>> >>> Thanks in advance. >>> >>> -- >>> Steve >>> >> >> > -- Peter M. Wolanin, Ph.D. Momentum Specialist, Acquia. Inc. peter.wola...@acquia.com
