To add to Chetan comment, I am working on an enhancement that offloads
bufferserver spooling to disk to a separate thread. This thread will
kick in when only half (should it be configurable?) of memory blocks are
left available. This should further avoid possibility of I/O spikes.
Vlad
On 8/24/15 14:16, Chetan Narsude wrote:
The bufferserver writes pages to disk *only when* it runs out of memory to
hold them.
Can you elaborate where you see I/O spikes?
--
Chetan
On Mon, Aug 24, 2015 at 12:39 PM, Atri Sharma <[email protected]> wrote:
Folks,
I was wondering if it makes sense to have a functionality in which
bufferserver writes out data pages to disk in batches defined by
timeslice/application window.
This will allow flexible workloads and reduce I/O spikes (I understand that
we have non-blocking I/O but it still would incur disk head costs).
Thoughts?
--
Regards,
Atri
*l'apprenant*
