updates on a key should not shift store operation time
Authored a new section: Performance on AWS.
use replace in coalesced write-behind-queue
New section added to index.
Revision History reset to make it ready for 3.5
FAQ item moved to Performance chapter.
update old value in coalesced write-behind-queue
Merge pull request #4343 from ahmetmircik/fix/3.5/shiftedStoreTimeFixer

Updates on a key should not shift store operation time
set min. store operation count to 2
copyedit
copyedit
copyedit
if both keys fall into same partition, events are batched. test fix
copyedit
copyedit
Revision History updates.
refactored test testMapLoader_withMapLoadChunkSize and increased test timeout
map replication operation was not removing elements from the backup and this leads to read of stale data if read backup is enabled
refactored test testMapLoaderLoadUpdatingIndex
assertTrueEventually check added to rarely failing test testEventOperationCount