Originally Posted by nextri

Yeah, we do have performance issues. Growing pains if you will, but we do know how to handle them also. Restructuring and optimizing huge databases isn't something we can just do in an hour or so. We need to do proper tests, and make sure we upgrade without breaking something. There has been many areas in which we've done improvements during the last few days, and we will do even more for the next few days. You can't rush development like this.

The error you got was only in the backend system for a couple of minutes, and didn't effect the system itself.

Feel free to look for other alternatives, if you can find any, but I'm confident that once these upgrades are complete, it will be smooth sailing from here.