3 ms·
The computation for the orange usernames was destroying performance. Not directly, but because it caused a lot of stuff to get loaded from disk that would not
by pg 18y ago
The computation for the orange usernames was destroying performance. Not directly, but because it caused a lot of stuff to get loaded from disk that would not otherwise have been. So I've temporarily turned the feature off till I can write a more efficient version.
- Shamiq 18y agoDo you mind posting the current code for it? I'm sure some of us would love to give optimization a shot.
- palish 18y agoOptimizing a program via messageboard would be like writing a program by mail.
- pg 18y agoI appreciate the offer, but it's not the kind of optimization that consists of taking one chunk of code and making it faster. The answer will consist of several little changes spread out throughout the code.
- tlrobinson 18y agoIt seems like it is something that could be computed once every few hours and cached without affecting the experience.
- jonursenbach 18y agoHow come you just didn't do the computations as a background process and let it run when each new comment comes in?
- lsb 18y agoApropos of this, has anyone had success by swapping a platter-based disk drive for a SSD?
- andreyf 18y agocaused a lot of stuff to get loaded from disk that would not otherwise have been Why not just keep it all in memory? We talk a lot, but it doesn't seem like the database should be all that large...