performance - what are the best ways to mitigate database i/o bottoleneck for large web sites? -
for large web sites (traffic wise) has alot of incoming reads , updates end being database i/os, what're best ways mitigate performance impact? 1 solution can think of - write, cache , delayed write (using separate job); read, use memcached concept. other better solutions?
here common solutions database performance:
- caching (memcache, etc)
- add memory database
- more database servers (master/slave or sharding)
- use different database type (nosql, redis, etc)
- indexes speed read perf. (careful, many affect write performance)
- ssds (fast ssds lot)
- raid
- optimize/tune sql queries
Comments
Post a Comment