What is making us slow (for the first time, after an idle period)?
What is making us slow (for the first time, after an idle period)?
Join the DZone community and get the full member experience.
Join For FreeRavenDB vs MongoDB: Which is Better? This White Paper compares the two leading NoSQL Document Databases on 9 features to find out which is the best solution for your next project.
We recently covered this question in several iterations in the ravendb mailing list.
The actual content of the discussion wasn’t so interesting as the number of ways idle time can make you life… interesting. In order to avoid having issues with idle time, you need to:
- Disable IIS unloading for inactive websites.
- Disable RavenDB unloading for inactive databases.
- Make sure that the HD doesn’t spin down during inactivity.
- You need to make sure that the system doesn’t got to idle / hibenration.
- Check that the server hasn’t been paged.
- Check that the CPU hasn’t moved to low power mode.
- Check authentication timeouts.
In the end, it was actually the last one that caused the problem. By default, Windows Auth token expire after 15 minutes, so you have to re-authenticate again, and that may make the first query after a while a little slower.
Just for fun, by default, all of the above happen. And that is just when running on a physical machine. When running on VMs (or in the cloud), you need to do all of those checks for the VM and the host machines.
Do you pay to use your database? What if your database paid you? Learn more with RavenDB.
Like This Article? Read More From DZone
Published at DZone with permission of Oren Eini, CEO RavenDB , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}