SeanTAllen changed the topic of #wallaroo to: Welcome! Please check out our Code of Conduct -> https://github.com/WallarooLabs/wallaroo/blob/master/CODE_OF_CONDUCT.md | Public IRC Logs are available at -> https://irclog.whitequark.org/wallaroo
_whitelogger has joined #wallaroo
pzel has joined #wallaroo
<slfritchie> Happy Friday, everyone. I'm the author of a blog article published today, "The Treacherous Tangle of Redundant Data: resilience for Wallaroo".
<slfritchie> A few weeks ago, John Mumm wrote an article that described what Wallaroo does to be resilient in case of a rebootable crash. But what if the crashed worker cannot reboot? Today's article describes the data redundancy technique that permits a Wallaroo cluster to recover after a crash with catastrophic data loss.
<rkallos> Thanks, slfritchie! I really enjoyed reading it. I am interested to see what the performance difference would be between Python-DOS and Pony-DOS :)
rkallos has quit [Quit: WeeChat 1.7.1]
<slfritchie> Thank you! My guess is that the biggest gain would be when multiple (far more than 2) clients are doing stuff, causing interference by the Python GIL.
pzel has quit [Ping timeout: 252 seconds]
pzel has joined #wallaroo
pzel has quit [Ping timeout: 245 seconds]
puzza007 has quit [Quit: ZNC 1.8.x-nightly-20180930-b00cc309 - https://znc.in]
puzza007 has joined #wallaroo
aturley has quit [Read error: Connection reset by peer]
aturley has joined #wallaroo