> For the complete documentation index, see [llms.txt](https://documentation.hak5.org/bash-bunny/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.hak5.org/bash-bunny/writing-payloads/cpu-control.md).

# CPU Control

From firmware version 1.3 onwards, the CPU may be controlled using the `CUCUMBER` command. By default, `CUCUMBER` is set to `DISABLE` - which sets the CPU governor to 'ondemand'. This is a good balance between performance and power draw with all cores scaling as needed.

To avoid excess heat buildup with payloads which require long term deployments, use `CUCUMBER ENABLE` to disable all but one CPU core and set the governor to 'ondemand'. This will keep the Bash Bunny cool as a, vegetable of choice.

To set the Bash Bunny to maximum performance, `CUCUMBER` may be set to `PLAID`[.](https://www.youtube.com/watch?v=mk7VWcuVOf0) This enables all cores and sets the governor to 'performance'.

| **MODE**           | **Setting**             | **Notes**                           |
| ------------------ | ----------------------- | ----------------------------------- |
| `CUCUMBER ENABLE`  | Single core 'ondemand'  | Low power for long term deployments |
| `CUCUMBER DISABLE` | Quad core 'ondemand'    | Default setting                     |
| `CUCUMBER PLAID`   | Quad core 'performance' | Beyond ludicrous speed              |

Much like `ATTACKMODE`, the CPU may be controlled dynamically in a given payload. This means that, for example, one stage of an attack may use the lower power `CUCUMBER ENABLE` setting while another may use the higher power `CUCUMBER PLAID` setting.