We’ve all worked under the PHB, but more common is the high level manager who, when faced with the dangers of problems of managing a large computing facility, begins to look for silver bullet solutions to problems. This blog post from James McGovern lists the top 10 mistakes that CIOs face when faced with this dilemma.
IPv6 is going to happen and many of us wish it were here faster, yet
nearly a decade after the transition began, most of us aren’t on IPv6
networks and have no immediate transition plan to do so.
This entertaining and informative set of slides shows the problem we’re
facing in IPv6 and practical steps we can take to help move the
Some takeaway lessons from the talk are:
- Separate services across hosts
- Scale each component separately
- Avoid large database replication by using internal pre-indexing of data across databases
- Let your services fit your needs (ie use both an IP and an HTTP filter for different problems)
- Storage is key, eg their use of both NetApp, mySQL replication and internally developed storage system MogileFS
- Cache is key, use Memcached
- Measure and monitor all aspects of the system for availability and planning
This talk is from 2004. We can only speculate to how things have changed since.
Toward the end of the talk, Paul shifts to a mainly system-oriented focus on optimization and presents a few tips:
- Increase the number of spindles
- Use software RAID striping for increased performance
- Eliminate non-database read-cache
- Use predictive selects to help optimize cache
- Use Memcached
- Reduce serialization by reducing/eliminating non-master nodes
You can listen to the talk here
or watch the video.