Hi,
CUBA scheduling uses SQL queries like “select from SYS_SCHEDULED_TASK … for update” for coordination. It leads to write activity.
Also, CUBA scheduling writes to the SYS_SCHEDULED_EXECUTION table, if you enabled “singleton” or “log start”, “log finish” flags in the task.
Noted that this is the expected behavior, thank you for your explanation. I get write activity almost each second - does this seem reasonable? (This is constant regardless of the scheduling interval).
I changed cuba.schedulingInterval to 60,000, but I still get database disk write activity constantly (or at least every second as monitored by iotop). Is this also expected?
I would suggest to enable “eclipselink.sql” debug logging in the CUBA app, and enable PostgreSQL logging for all SQL queries, to see what queries does PostgreSQL server receive.
Note that due to the MVCC or other reasons it is completely normal for PostgreSQL server to write some disk pages even during execution of READ queries or even when the server is idle.
See: