everyone knows about -funroll-loops and -funsafe-math-optimizations, but the real winner here is posix_fallocate
-
-
calling abort is a perfectly reasonable (and likely *the only* reasonable) thing to do if you find that an internal invariant is violated
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Also lots of crap applications use sqlite not for valuable data but just cache junk, in which case performance matters and throwing away a corrupt db is no big deal.
-
They would need to discard it when starting up with the assumption that it's corrupt if they've disabled all the consistency / integrity guarantees. They could also just not use tons of transactions or use WAL mode with a database connection left open. It performs well enough.
End of conversation
New conversation -
-
-
They might get hit by something like SIGKILL through no fault of their own though. You would usually be using an in-memory SQLite data store if it was just temporary. Could only see wanting to use it without any integrity / robustness if it's temporary + too big to fit in memory.
-
i.e. you're going to discard the entire thing afterwards no matter what anyway. It makes sense that they support the somewhat insane modes but if you search around there's software using those just because it's faster without really thinking about it.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.