Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Is there something you can point to that explains this "flush them to the durable DB once in a while" pattern in more detail?


Instead of running each small write query as the event occurs (a vote), collect them in memory and at some time interval (1m, 5m, or whatever your UX will tolerate) write them to the DB in batch with one (or a few) writes.


Thank you. This fits a current need of mine perfectly.

Do you have any other helpful tips you’d like to share? Any thoughts between Redis and Memcache?


Not the GP, but if the GP described a scenario that is useful to you, redis can #1 act as the memory cache if the processes themselves don't last long enough for the optimization to be useful, and #2 can act as a cheap message queue to funnel similar requests into a single (or small number of) processes for aggregation before writing to disk.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: