3 ms·
This being C, I assume the performance is really good FWIW, everyone I know who moved web-serving things to C did so primarily because of latency, and then sec
by ktRolster 10y ago
This being C, I assume the performance is really good
FWIW, everyone I know who moved web-serving things to C did so primarily because of latency, and then secondarily to avoid GC time delays. Higher transactions per server was a bonus, but no one did it for that.
Also, if you have to hit a database, then any efficiency you get from switching to C will probably be swallowed up by that.
- woodman 10y ago> Also, if you have to hit a database... I can only think of one case where that is pretty much always true - CRUD with a network connected db backend, several cases where it is debatable, and a bunch of cases where that is wrong. See sqlite3, situations where you can use unix sockets, dynamically loaded modules, etc. I'm finishing up a project that basically builds state models from log events, automatically, and robustly enough that hopefully the end users wouldn't notice if I were run down by a bus. With the massive amount of data and high dimensionality of the problem, I have a hard time seeing how to pull it off but with C and statically compiled sqlite... or a big bag of money to throw at IBM.
- ktRolster 10y agobuilds state models from log events, automatically That sounds really cool, but I'm not quite sure what it means.
- woodman 10y agoTake business process modeling [0], and add a dash of directed acyclic graph [1]. You need both fast access to a massive amount of historical data, and the ability to finely control what gets stored where in memory - so not something you can really do in an SQL transaction. [0] https://en.wikipedia.org/wiki/Business_process_modeling https://en.wikipedia.org/wiki/Business_process_modeling [1] https://en.wikipedia.org/wiki/Directed_acyclic_graph https://en.wikipedia.org/wiki/Directed_acyclic_graph