What are the current pain points in serving Less Wrong? Reddit’s made some significant performance improvements since the code was forked, including implementing Markdown in C rather than Python, and using Cassandra for in-memory caching—would it be worth it to look through these changes and see if any make sense to apply to Less Wrong?
ETA: For example, I could probably isolate and apply the Markdown changes if it was likely to be useful.
The largest pain point has been instability in the paster process. The new deployment (as of a couple of ours ago (2010-06-09)) should roll out a new application server if that happens again.
Processor load has not been a problem, so improvements to the efficiency of the Markdown parser will have minimal impact unless traffic grows a lot.
(Thanks for your offer of assistance, and sorry about the late reply.)
What are the current pain points in serving Less Wrong? Reddit’s made some significant performance improvements since the code was forked, including implementing Markdown in C rather than Python, and using Cassandra for in-memory caching—would it be worth it to look through these changes and see if any make sense to apply to Less Wrong?
ETA: For example, I could probably isolate and apply the Markdown changes if it was likely to be useful.
The largest pain point has been instability in the paster process. The new deployment (as of a couple of ours ago (2010-06-09)) should roll out a new application server if that happens again.
Processor load has not been a problem, so improvements to the efficiency of the Markdown parser will have minimal impact unless traffic grows a lot.
(Thanks for your offer of assistance, and sorry about the late reply.)