教你50招提高ASP.NET性能（十六）：把問題仍給硬件而不是開發人員

(27)Throw hardware at the problem, not developers

招數27：

把問題仍給硬件而不是開發人員

As developers, we often want to fix problems with code, but don’t be afraid to ‘put the compiler down’ and throw some hardware at the problem.
做爲開發人員，咱們一般想經過代碼解決問題，但不要懼怕‘批評編譯器’和把問題仍給硬件。

Performance problems caused by disk I/O bottlenecks or paging out of RAM can often be solved by a faster hard drive or more RAM. CPUbound bottlenecks can often be solved by a new machine with a faster processor.
因爲磁盤I/O瓶頸或者分頁內存泄露引發的性能問題一般能夠經過更快的硬盤驅動器或更多的內存解決。CPU密集型瓶頸一般能夠經過一個新的裝有更快速度處理器的機器解決。

As counterintuitive as it sounds, addressing problems by buying a new machine or upgrading an aging one is often much cheaper than having a developer troubleshoot, diagnose, and correct a deep performance problem. And the rest of your website will get a performance kick to boot!
這聽起來有違直覺，診斷並修正一個深層次性能問題，經過購買新機器解決問題或者升級老化的部件一般比讓開發人員解決問題成本低的多。而且你的其餘網站會獲得一個性能提高。