RavenDB-1500 Page finding optimization - try to reuse last found page
RavenDB-1500 When you reuse a page then add to the cursor lazy pages - they will be used only if the page splitter needs them
Merge branch 'voron' of github.com:ayende/raven.voron into RavenDB-1500
Fix API usage
Use MDB_APPEND on sequential writes
Minor
Merge branch 'RavenDB-1500' of github.com:ayende/raven.voron into voron
Instead of storing a lot of lazy pages, just make the cursor itself lazily created
Make sure that we use the current page instance if we already have it
Provider a lazy implementation that allow deferral of mutations
Moving to a better method of handling the actual update