On Tue, Jan 7, 2014 at 12:18 PM, Amir Taaki <genjix@???> wrote:
> Are you running an HDD or SSD? If it's an HDD and the write throughput
> is low that blocks are not being indexed/written fast enough, then the
> memory buffer is filling up as new blocks are queued in the database.
>
> The only way to resolve that (if it's the problem) is by a) making pure
> writes faster or b) indexing less data (not a fan of this) [note: not
> pruning but just not indexing].

There is a third option: throttle the networking component so the
writer can keep up. You control the rate at which "getdata" messages
are sent, so you can limit those to whatever the writer can handle. I
think this is the real solution. Having faster writes is nice too, but
it just makes the race condition less likely.

-William