3 ms·
... and then you have to deal with all the concurrency and blocking issues that come with outsourcing your timeslicing. Timeslicing isn't hard. It's even simpl
by axod 17y ago
... and then you have to deal with all the concurrency and blocking issues that come with outsourcing your timeslicing.
Timeslicing isn't hard. It's even simpler if you're the one writing the code.
If you are in the horrible position of having to interface with blocking/crashing code though, great shame :(
- andrew1 17y agoOne of the big pains of my work day is our accounting system which, while being great at what it does well, can be abysmally slow to respond to queries (the simple question of how much of X do we own now, takes it around three minutes to answer...). We know from experience though that internally it can deal with up to three requests at a time without it slowing down. If I only had one thread then three requests (which block) would take me nine minutes to process, with three threads I can get all the results back in three minutes.
- axod 17y agoInterfacing with a broken bad interface is never fun. But perhaps fix the problem instead of working around it and letting it spread...
- andrew1 17y agoUnfortunately that's not practical, it's third party software and at least the last time we checked there wasn't a better alternative with the same functionality.