Fixing huge memory consumption when the restore of a database with esent storage was requested and 'defrag' option was selected. The problem was that system db didn't have any indexes but we added Raven/Restore/Status documents to the prefetching queue - so they were never taken from there.
Introducing a throttling when calling esent compaction callback. The frequency of updating the Raven/Restore/Status document in this case just incredibly slowed the process down.
Merge pull request #1417 from arekais/huge-memory-consumption-when-restore-with-defrag

Huge memory consumption when restore with defrag