The Freesound Blog

Hi all,

Freesound has been struggling to regain stability over the last few weeks but we are happy to announce that we finally made it:) The problems started about a month ago when we realized our DB configuration was completely wrong for our hardware and the kind of traffic we are serving. After fiddling around with it we settled for a setup that seemed to work OK. Even so, problems didn’t stop with the sounds page 404ing at times, resulting in the whole site 404ing. We’ve finally pinned this down to some horribly constructed queries our Django ORM was doing for us…

After we rewrote those queries the load average of the DB server was reduced dramatically as you can see from this beautiful Munin graph which shows the load average before (pre 18:00) and after (post 18:00) we deployed the version with the fixed queries 🙂

Essentially these changes made the site more stable but our problems were far from over. Load average on our webserver machine was off the roof, making impossible for any sane sysadmin to sleep… While checking web servers logs we found repeated error of broken connections… This time the culprit seemed to be the flup module that Django uses by default to serve fastcgi. All efforts to isolate this problem proved fruitless and we finally decided to ditch flup and move to Gunicorn which in general is a good idea concerning how things are moving in the Python world. After a period of testing we deployed to production the 3rd of November and are happy to announce that the results are really good! Have a look at the graph below. Load has dropped from peaking at 11! to peaking at 4! and being most of the time at around 1. Which is expected and acceptable for the limited hardware we are running on.

So sorry for the long technical post but we really felt we had to give an explanation for the poor service you’ve seen lately. With this stability we’re back at working on application bugs and even better new features 🙂

Thanks

Stelios

Hello all, a quick blog post to tell you all we are currently experiencing some problems with freesound. We’re very busy trying to figure out what exactly is going wrong and it looks like our database server is badly configured…

Hold on while we tweak the settings! You might experience some glitches or more downtime today…

Due to some needed operations on the server, we will be closed for maintenance, starting today at 12h GMT+2. Hopefully the down time will last only a few hours.
You have been warned!

Dear Freesounders,

For more than a year now we’ve been promising you an upgrade of
freesound. Dates got shifted into the future, things took (much)
longer than expected, … About half a year ago everything shifted
into higher gear when the team of Vincent, Gerard, Frederic,
Stelios and Jordi started getting involved deeply in freesound code.

Stuff starting whizzing along, more work was done than ever on
freesound “2” or “nightingale”, or now just… freesound.org again. So
many things were rebuilt, reenvisioned and reimplemented that it would
be rather useless to try to list them all. But let it be clear that we
started from zero: the old -and relatively broken- codebase was
replaced by a bright shiny new one, based on the great django
framework.

We know the new site creates emotional responses as you have been
working so closely with the old one. For us it’s such a big change
which will let freesound “breathe” again.

Hopefully this new freesound site will serve us for many years to
come. For us (the people behind the scenes) the biggest advantage to
this new site is probably the maintainability: it will be so much
easier to adapt the code, add new features, fix bugs…

Talking about bugs: feel free to post bugs in this forum or via the
contact form.

Thanks for waiting and special thanks to the beta testers!

Greetings,

– The Proud Freesound team (Bram, Gerard, Vincent, Jordi, Frederic,
Stelios and Xavier)

Congratulations freesound!! We have just reached 100,000 sounds!!!!! 🙂