# Cpuset.conf - setup

**URL:** <https://forum.scylladb.com/t/cpuset-conf-setup/4433>\
**Category:** ScyllaDB\
**Tags:** upgrade, configuration\
**Created:** [February 1, 2025, 5:42pm UTC](https://forum.scylladb.com/t/cpuset-conf-setup/4433 "2025-02-01T17:42:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bryam](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@bryam](https://forum.scylladb.com/u/bryam)\
**Post date:** [February 1, 2025, 5:42pm UTC](https://forum.scylladb.com/t/cpuset-conf-setup/4433/1 "2025-02-01T17:42:10Z")

</div>

_Upgrade from 5.0 to 5.1_  
#ScyllaDB version: 5.1  
#Cluster size: 3 nodes  
#os amazon Linux 2023

Hello team, I am following documentation [Upgrade Guide - ScyllaDB 5.0 to 5.1 | ScyllaDB Docs](https://opensource.docs.scylladb.com/branch-5.1/upgrade/upgrade-opensource/upgrade-guide-from-5.0-to-5.1/upgrade-guide-from-5.0-to-5.1-generic.html) and to complete upgrade, it seems I have to change Mode in perftune.yaml.

When I execute command “sudo scylla\_sysconfig\_setup --nic ens5 --homedir /scylla --confdir /scylla/config” file /etc/scylla.d/cpuset.conf is generated. After that I restart scylla service and /etc/scylla.d/perftune.yaml is generated.

```auto
cat /etc/scylla.d/cpuset.conf
CPUSET="--cpuset 0-1 "

cat /etc/scylla.d/perftune.yaml
cpu_mask: '0x00000003'
mode: mq
nic:
- ens5
tune:
- net

```

it suppose to be mode `sq_split` but instead it is mq. wonder if there is something wrong with command and/or current config?

btw, cluster is up and running but trying to complete scylladb documentation and tune best as possible ec2 instance type i4g.large.

Thank you

---

<div class="post-metadata">

**Author:** ![Gabriel](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/gabriel/32/60_2.png) [@Gabriel](https://forum.scylladb.com/u/Gabriel)\
**Post date:** [April 18, 2025, 7:38am UTC](https://forum.scylladb.com/t/cpuset-conf-setup/4433/2 "2025-04-18T07:38:20Z")

</div>

Hi @bryam ,

You are running an old and non-supported version of ScyllaDB,  
I suggest you gradually upgrade to at least ScyllaDB 6.2 and execute the command again.

BR,  
Gabriel