The ability to the CPU usage of caused by indexing in searchcode server can only be done through paid for editions of searchcode server by modifying the "Backoff Value" inside the settings page. It is possible to control the general amount of CPU usage for the process using OS specific commands such as cpulimit for linux.

If you want to launch searchcode server on a multi-tennancy system setting this value is highly advised. It can also be worth setting on t2 instance types in AWS to ensure that all credits are not used. The value to set should be set to the amount of CPU's you want to restrict searchcode server to be able to use. On a t2.large instance to ensure that the instance will never run out of credits a value of 0.2 will achive this. Keep in mind that the CPU load average is a global setting, and as such other applications can impact it. By setting the value too low in a multi-tennancy situation you can starve searchcode of CPU and the ability to index. Be sure to monitor your instance if you set this value. A sure sign of it being too low is the message "Indexing paused" appearing in the logs.