Several system configuration settings should be applied. For ease of use, the necessary scripts and configuration files are provided. Files are under dist/common and seastar/scripts in the Scylla source code, and installed in the appropriate system locations. (For information on Scylla’s own configuration file, see Scylla Configuration.)

If Scylla is installed on an Amazon AMI, the bootloader should provide the clocksource=tsc and tsc=reliable options. This enables an accurate, high-resolution Time Stamp Counter (TSC) for setting the system time.

This configuration is provided in the file /usr/lib/scylla/scylla_bootparam_setup.

It is highly recommended to enforce time synchronization between Scylla servers.

Run ntpstat on all nodes to check that system time is synchronized. If you are running in a virtualized environment and your system time is set on the host, you may not need to run NTP on the guest. Check the documentation for your platform.

If you have your own time servers shared with an application using Scylla, use the same NTP configuration as for your application servers. The script /usr/lib/scylla/scylla_ntp_setup provides sensible defaults, using Amazon NTP servers if installed on the Amazon cloud, and other pool NTP servers otherwise.

When installing Scylla it is highly recommanded to use the the scylla_setup script.
Scylla should not share CPUs with any CPU consuming process. In addition on AWS, we recommend pinning all NIC IRQs to CPU0 (due to the same reason). As a result, Scylla should be prevented from running on CPU0 and its hyper-threading siblings. To verify that Scylla is pinning CPU0 use the command below:
If the node have four or less CPUs don’t use this option.