lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetic <>
Subject Re: High response time after being idle
Date Wed, 28 Dec 2011 23:45:11 GMT
Right, I think that's what's happening here.
Google "swapiness" if you are on Linux.

Alternatively, one could add something to prevent the OS from swapping out Solr's process. 
Here is how ElasticSearch does it, for example:


Performance Monitoring SaaS for Solr -

> From: Erick Erickson <>
>Sent: Wednesday, December 28, 2011 5:07 PM
>Subject: Re: High response time after being idle
>What else, if anything, do you have running on the server?
>Because it's possible that pages are being swapped out
>for other processes to use.
>Solr itself shouldn't, as far as I know, time out anything so I
>expect you're running into issues with the op system.
>On Wed, Dec 28, 2011 at 10:25 AM, Gora Mohanty <> wrote:
>> On Wed, Dec 28, 2011 at 8:52 PM, Odey <> wrote:
>>> Hello,
>>> I'm running Solr 3.5 on a XAMPP/Tomcat environment. It's working pretty good
>>> for just one exception: when Solr remains idle without handling any requests
>>> for about 5-10 mins the first request sent again will be delayed for a few
>>> seconds. Subsequent requests are lightning-fast as usual. So it seems to me
>>> like something important has been shut down while staying idle and has to be
>>> reloaded.
>> [...]
>> Is it possible that the system is running out of RAM, and swapping,
>> or is aggressively swapping for some reason?
>> Regards,
>> Gora
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message