Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
What it comes down to is not CPU speed but rather memory bandwidth. You want as much cache on your CPU as possible. Bigger L1, L2, L3 lead to better megabase performance. The more stuff in your base, the more memory required, and the more of your base exceeds your available cache size the more the CPU has to pull stuff from your RAM. It is this RAM access that slows you down the most.
So, while the necessity of producing more and more stuff is unavoidable if you want higher SPM, you can try to minimize the performance impact from having excess active chunks or more biter groups pathfinding along your borders in order to keep RAM access to a minimum.