The attached screenshot shows the transition on a master 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 increased load expected from the stats.jsp page, or would your consider this a bug? Other than creating a custom jsp page with just a subset of this data, is I don't see any way in Solr to query and display specific stats of interest for one core via the REST interface - am I missing something? Thanks, Peter -- Peter M. Wolanin, Ph.D. Momentum Specialist, Acquia. Inc. peter.wola...@acquia.com
