What is New in RavenDB 3.0: Operations - Optimizations
Join the DZone community and get the full member experience.
Join For Freeone of the important roles operations has is going to an existing server and checking if everything is fine. this is routine maintenance stuff. it can be things like checking if we have enough disk space for our expected growth, or if we don’t have too many indexes.
here is some data from this blog’s production system:
note that we have the squeeze button, for when you need to squeeze every bit of perf out of the system. let us see what happens when i click it (i used a different production db, because this one was already optimized).
here is what we get:
you can see that ravendb suggest that we’ll merge indexes, so we can reduce the overall number of indexes we have.
we can also see recommendations for deleting unused indexes in general.
the idea is that we keep track of those stats and allow you to make decisions based on those stats. so you don’t have to go by gut feeling or guesses.
Published at DZone with permission of Oren Eini, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Comments