Spin wait timeout when running save-data on aws micro instance about cointrader HOT 3 CLOSED

The only difference with the console mode is saving to the database. If it's Book data, then a diff is also calculated but that shouldn't take long. Some full Book snapshots are up to 500k in the database, so it might be that such a large record takes more than 100ms to send over the network, save to the DB, and return a confirmation. If it really is that slow (just a hypothesis), then I don't see what could be done for AWS freebies. Spinning up a thread in the background to batch & flush DB inserts wouldn't help, I guess?

from cointrader.

Hi tim,

Indeed it is the inserts taking a while. Unless you have any objection i will change the persitutil to use a thread pool and loog an error if not persited with a timeout set in the config file.

from cointrader.

I thought there was already a separate insert thread? Maybe I'm thinking
of another project... Definitely a good idea.

On Mon, Aug 11, 2014 at 11:56 PM, douggie [email protected] wrote:

Hi tim,

Indeed it is the inserts taking a while. Unless you have any objection i
will change the persitutil to use a thread pool and loog an error if not
persited with a timeout set in the config file.

—
Reply to this email directly or view it on GitHub
#62 (comment).

from cointrader.