This is a most excellent place for technology news and articles.
Man, logging issues are like baby's first engineering problem... That's just embarrassing
These are the people trying to tell you programming is a solved issue btw.
All things are solved by lowering your standards far enough.
AI Cartel: we will buy all your stock
Memory Cartel: yaaaay!
MC: but now nobody is building computers, hurting our storage business :(
AC: we gotchu fam, we will just make our systems outrageously system demanding, killing components and driving sales
MC: yaaaaaaaay
eating their own dog food, are they?
they'll have to hire an actual developer to fix it.
If you're on Linux and aren't particularly fussed about any issues stemming from power loss, you can probably run it under eatmydata and it'll disable SQLite calls to fsync().
it's weird who gets reported for this stuff.
There was a game that released not too long ago that was spamming the same message to it's log file in 500 millisecond intervals doing a constant stream of write and flush to disk the entire time the game ran.
silence.
There may be a minor difference in the size of the user base
There's a pretty massive difference in scale and impact here..
Can you explain how you came to that conclusion? I don't know what game it was and how many copies it sold, nor how many Codex users there are, but I assume you already know those details?
500 milliseconds is an eternity in computer time. Doing a 10KB write (very generously large for a logfile) write every 500 milliseconds is something it could do continuously for about 1,000 years before it used up the write capacity of an SSD.
The game was Windrose and it was making over a hundred gigabytes of unnecessary writes per hour at 90,000-130,000 writes per second, for the record.
After the devs tweaked their database caching it went down to 'only' 20-60 writes per second, which still feels insane to me.
They can't have been talking about Windrose either, then, because they very clearly said it was writing log file entries every 500 milliseconds. Either they misunderstood the scale too, or they were talking about a different issue, because 500 milliseconds is definitely not on the same scale as what Codex or Windrose are being accused of. The game issue they described is not comparable to either of those scenarios.
cue the scene from Airplane 2 where the Steward explains they have been knocked of course by just a "tad"
