Once you get around 500+ GBs of traffic to a server with multiple projects on you either have a) only static files b) hopefully have a good setup for database indexes, object caching CMS and such…
I deploy a separate 10k SCSI cache-disk – outside the RAIDs for those object caching tasks and believe me or not – even these disks are too slow… (next step would be a RAID0 stripe) and I just kicked out the last SATA based Dual XEON server… (having the 2nd HD failure on that SATA crap)
Today I realized that the standard RedHat Enterprise 3 deployment is a bit setup like a desktop system.
Some nice links to read up…
ext3's data=journal mode is incredibly well-suited to situations where data needs to be read from and written to disk at the same time. Therefore, ext3's data=journal mode, which was assumed to be the slowest of all ext3 modes in nearly all conditions, actually turns out to have a major performance advantage in busy environments where interactive IO performance needs to be maximized.
and a quick-step how to apply the tricks above (no warranties as usual)
Recent comments
1 year 35 weeks ago
1 year 35 weeks ago
1 year 37 weeks ago
1 year 38 weeks ago
1 year 38 weeks ago
1 year 47 weeks ago
1 year 47 weeks ago
1 year 48 weeks ago
1 year 48 weeks ago
1 year 49 weeks ago