Make 43 Things Faster

We are in process of replacing web servers which some of them have been with us since the beginning and adding a new ones.

- 7 new servers will be put into production by the end of next week.
- adding 28G of memory for memcache
- planning to switch master db with a slave db box since it’s newer and faster
- going to re-index entries and comments tables
- changing architecture of www.43places.com, www.allconsuming.net, www.43people.com and www.listsofbests.com setup to offload traffic from master database to farm of slave servers
- planning to speed up search by doing it locally on each box rather then doing it across NFS mounted drives
- I can not forget about the code optimization in progress

Hopefully this all will contribute to speed and stability of 43T.

Man I love doing Webkinz but it loads too slow. Luckliy with this in my hands I’m sure to get this done

I just started please remind me

I’m doing a bunch of refactoring. Today I’m turning a lot of code that looks like this:

if thing.nil? || thing.empty?

into this:

if thing.blank?

We’re not quite done with the new database load balancing setup, but one side effect of what we’re working on is that pages are about 25-50% faster for logged in users. You can check out Ivan’s diagram of the setup on the blog:

http://blog.robotcoop.com/2008/02/27/load-balancing-act/

For a 4 day class focusing on performance tuning. We’ve already found 2 things that we can try…

We’re taking a 3 day class about “MySQL High Availability”. The first day was mostly stuff we already know about replication, but we should start covering clustering which should be interesting.

It took a little bit, but with Ivan’s help, things seem pretty fast and stable now.

Sweetness!

other than talking with Ivan, Laurel, Josh, Todd & Buster. The sites seems pretty zippy now so I’m marking this off my list.

In addition:
- we added an extra RAM to our master and slave DBs bringing it to 16G each
- added extra indexes to couple of tables
- added 8G of memory to memcache
- de-normalized some of our tables
- added more front end caching
The fight continues on.