Skip to main content

Other Recommended Settings

Every implementation is different — some sites have a couple of production lines, others have hundreds. You may only make one product or thousands. Regardless, here are some settings we recommend starting with.

Set WebSocket max memory size to 4096​

Perspective views pass data to popups via websockets. If you have a large number of materials or assets, you may want to increase the max memory setting.

This forum post explains how to update ignition.conf to do this:

Enable “Include Schema in Table Name” for the kanoaCore database connection​

In the kanoaCore database connection configuration (Advanced Properties), we recommend enabling:

  • Include Schema in Table Name

Adjust the User Inactivity Timeout​

In the Gateway settings, we recommend reviewing and adjusting the User Inactivity Timeout:

  • Gateway → Security → General

Enable Database Concurrency​

We recommend switching on READ COMMITTED SNAPSHOT ISOLATION (RCSI) in Microsoft SQL Server.

Enabling this feature:

  • Helps avoid Reader/Writer blocking - In default mode, a SELECT can block or be blocked by an UPDATE, INSERT, or DELETE. With RCSI, readers get a consistent snapshot without locking the table.
  • Reduces Deadlocks - Because RCSI avoids shared locks, there's much less lock contention, and fewer deadlocks in high-concurrency environments.
  • Improves Read Scalability - Excellent for reporting queries, dashboards, APIs, or UIs that only need committed data and can tolerate a slight delay in seeing updates.

To enable RCSI, log into SQL Management Studio as a user with dbOwner permission on the Kanoa Core database and run the following:

SELECT is_read_committed_snapshot_on 
FROM sys.databases 
WHERE name = 'kanoaCore';

--USE master;
--GO

--ALTER DATABASE kanoaCore...
--SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
--GO

--ALTER DATABASE kanoaCore...
--SET READ_COMMITTED_SNAPSHOT ON;
--GO

--ALTER DATABASE kanoaCore...
--SET MULTI_USER;
--GO