Batch writes to history file

GoogleCodeExporter commented 9 years ago

Currently, we log blocked/allowed packets (depending on user settings) to
history.db on a real-time basis, as they happen.  For performance reasons
we should batch these up, and only write to the db once every N seconds so
that we can be more performant if the user has lots of network activity
going on.

No need for a real UI field to adjust this setting, we'll just put a field
in peerblock.conf that the user can adjust if need be (or if they want to
run their own performance-tuning tests).  We should be able to identify a
suitable default, and run with that for most users.

Original issue reported on code.google.com by peerbloc...@gmail.com on 19 Dec 2009 at 8:13

GoogleCodeExporter commented 9 years ago

I'm sure we only write to the history.db every 15 secs. They just get queued up 
until 
the timer runs out.

Original comment by nightstalkerz on 19 Dec 2009 at 9:09

GoogleCodeExporter commented 9 years ago

Oh, my bad - guess I should've looked into the code before I started to go 
adding new
bugs.  Thanks man!

Original comment by peerbloc...@gmail.com on 19 Dec 2009 at 9:13

Changed state: Invalid

warvair / peerblock

Batch writes to history file #228