Stepmania Online

The webchat code? I don't see why that would cause high CPU usage.

The CPU usage had to do with some of the webchat code that was copied over from a newer commit. Reveriting this and CPU usage is finally back to normal which means the site/server should *finally* be atleast as stable as sqlite was before it was running into the corruption problems (but likely more stable).

Thanks for the merge, I fixed the security issues, which I blame on being tired :)

I have a few more updates I have not pushed yet, and right now we are seeing some crazy CPU usage we are trying to debug, I will make a branch of the current codebase if you want to take a look.

Update: https://github.com/concubidated/OpenSMO/tree/smo.net

Sqlite was chosen because indeed it was standalone, and thus much easier to put on any kind of machine. I never thought that a big project like SMO.net would come to exist from it.. :)

I saw a pull request on Github that's apparantly what you're running now. Great, but it has a lot of errors and possible security holes. I recommend you don't run this version until you get the latest.

I was wondering whether or not a new version of OpenSMO would be released (1.05) that would change to MySQL.

ok kool :)

[quote="Charlo"]Is there a reason why SQLite was chosen in the first place? I've rarely seen it used; MySQL is far and away the most popular DB for open-source stuff.[/quote]

OpenSMO was originally developed as a standalone project. So Sqlite was a better option at the time. I dont think he expected it to get this big :)

Because it is easier to implement and integrate into c#. The issues we were having didn't make a lot of sense in the first place so it is still kind of strange that it was having problems.

Is there a reason why SQLite was chosen in the first place? I've rarely seen it used; MySQL is far and away the most popular DB for open-source stuff.

I finished porting over the OpenSMO code to run on MySQL instead of SQlite.

We are currently trying to stress test it to make sure all the changes are working correctly. After we are happy with it we will migrate all database over to the fancy new MySQL Database.

[b]Now running on the main server and site![/b]