3 ms·

Sorry the site's having issues. I haven't done any significant work on it in most of two years and there's rather a lot more data in it than when I actually wor

Sorry the site's having issues. I haven't done any significant work on it in most of two years and there's rather a lot more data in it than when I actually worked on it. So, yes, it's true, I haven't used the right tool for the job. Except that as with so many things "the right tool" is "an actively maintained codebase". Looking into why it's crashing now, but don't expect any miracles

DRMacIver 15y ago
Should be running (a bit) better now, though likely still on the slow side. Turns out a query I'd written back when there were 20k votes in the system didn't perform so well now that there are 200k votes in the system. Go figure.
- masenf 15y ago
  Scale is always one of the most difficult things for me to plan for. Over last summer I was working on a registration system for an ISP which worked really well in testing. Once the database exploded to over 1M rows however, that application's performance was noticeably suffering. Unfortunately now that system is live, and the schema can't be changed for a few months...oops