Hacker News new | past | comments | ask | show | jobs | submit login

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.



It seems like it is something that could be computed once every few hours and cached without affecting the experience.


Do you mind posting the current code for it? I'm sure some of us would love to give optimization a shot.


I 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.


Optimizing a program via messageboard would be like writing a program by mail.


Or like a programming competition.


That's how most open source development happened for a long time.


Apropos of this, has anyone had success by swapping a platter-based disk drive for a SSD?


caused 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...


How come you just didn't do the computations as a background process and let it run when each new comment comes in?




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: