Hi Family.  The stray cat y'all fed is back for more. (Picture a cat emoji  ;-)

I am reviving an old thread, with a question posted in 2009 and again in 2020.

I just reinitialized my IDS server (still playing with parameters) and I now have:

• ROOTSIZE 1000000
• PHYSFILE  200000
• LOGSIZE  25000
• LOGFILES 8
• RTO_SERVER_RESTART 0 # Was originally 60

So I am not concerned about how long it takes to restart. I just was trying to get rind of this advisory that I get anyway during initialization:

2023-07-19 18:01:52.761  Performance Advisory: Based on the current workload, the physical log might be too
small to accommodate the time it takes to flush the buffer pool.

if I run onstat -g ckp I get an even more ominous message, though the system has nothing going on:

$ onstat -g ckp

IBM Informix Dynamic Server Version 14.10.FC10DE -- On-Line -- Up 00:37:05 -- 537200 Kbytes
2023-07-19 18:38:37

AUTO_CKPTS=Off   RTO_SERVER_RESTART=Off

                                                                    Critical Sections                          Physical Log    Logical Log
           Clock                                  Total Flush Block #      Ckpt  Wait  Long  # Dirty   Dskflu  Total    Avg    Total    Avg
Interval   Time      Trigger    LSN               Time  Time  Time  Waits  Time  Time  Time  Buffers   /Sec    Pages    /Sec   Pages    /Sec
2          18:01:45  Startup    1:0x418           0.0   0.0   0.0   0      0.0   0.0   0.0   24        24      22       0      1        0
3          18:01:49 *User       1:0x12e7018       0.6   0.0   0.0   1      0.0   0.6   0.6   32        32      334      83     4839     1209
4          18:01:50 *User       1:0x19d6018       0.0   0.0   0.0   1      0.0   0.0   0.0   36        36      97       97     1775     1775
5          18:01:51 *User       1:0x20c5018       0.0   0.0   0.0   1      0.0   0.0   0.0   32        32      90       90     1775     1775
6          18:01:59  Admin      2:0xc6018         0.4   0.4   0.0   1      0.0   0.0   0.0   2479      2479    182      22     5245     655
7          18:07:13  CKPTINTVL  2:0x776018        0.2   0.2   0.0   0      0.0   0.0   0.0   507       507     382      1      1712     5
8          18:17:13  CKPTINTVL  2:0x778018        0.0   0.0   0.0   0      0.0   0.0   0.0   1         1       26       0      2        0
9          18:27:14  CKPTINTVL  2:0x77f018        0.0   0.0   0.0   0      0.0   0.0   0.0   7         7       14       0      7        0
10         18:32:14  CKPTINTVL  2:0x781018        0.1   0.0   0.0   0      0.0   0.0   0.0   1         1       25       0      2        0

Max Plog       Max Llog       Max Dskflush   Avg Dskflush   Avg Dirty      Blocked
pages/sec      pages/sec      Time           pages/sec      pages/sec      Time
10240          1280           0              517            63             0

Based on the current workload, the physical log might be too small
to accommodate the time it takes to flush the buffer pool during
checkpoint processing.  The server might block transactions during checkpoints.
If the server blocks transactions, increase the physical log size to
at least 716800 KB.

For what I'm doing, that's ridiculous!  The information I see in that morass above does not indicate any issue that might cause a problem, if I understood Art's explanation to ABeMie in 2020.  I do plan to move all the logs (and increase the size of logical logs) into another DBspace later but I still think 716MB is kinda overkill, even if I do run a minor application.

At this time, onstat -d shows ROOTDBS over 57% free

What other ONCONFIG parameter[s] can I tweak to get rid of this scare tactic?  Or just ignore it?

Thanks for ideas, folks.

Hi Family.  The stray cat y'all fed is back for more. (Picture a cat emoji  ;-)

I am reviving an old thread, with a question posted in 2009 and again in 2020.

I just reinitialized my IDS server (still playing with parameters) and I now have:

• ROOTSIZE 1000000
• PHYSFILE  200000
• LOGSIZE  25000
• LOGFILES 8
• RTO_SERVER_RESTART 0 # Was originally 60

So I am not concerned about how long it takes to restart. I just was trying to get rind of this advisory that I get anyway during initialization:

2023-07-19 18:01:52.761  Performance Advisory: Based on the current workload, the physical log might be too
small to accommodate the time it takes to flush the buffer pool.

if I run onstat -g ckp I get an even more ominous message, though the system has nothing going on:

$ onstat -g ckp

IBM Informix Dynamic Server Version 14.10.FC10DE -- On-Line -- Up 00:37:05 -- 537200 Kbytes
2023-07-19 18:38:37

AUTO_CKPTS=Off   RTO_SERVER_RESTART=Off

                                                                    Critical Sections                          Physical Log    Logical Log
           Clock                                  Total Flush Block #      Ckpt  Wait  Long  # Dirty   Dskflu  Total    Avg    Total    Avg
Interval   Time      Trigger    LSN               Time  Time  Time  Waits  Time  Time  Time  Buffers   /Sec    Pages    /Sec   Pages    /Sec
2          18:01:45  Startup    1:0x418           0.0   0.0   0.0   0      0.0   0.0   0.0   24        24      22       0      1        0
3          18:01:49 *User       1:0x12e7018       0.6   0.0   0.0   1      0.0   0.6   0.6   32        32      334      83     4839     1209
4          18:01:50 *User       1:0x19d6018       0.0   0.0   0.0   1      0.0   0.0   0.0   36        36      97       97     1775     1775
5          18:01:51 *User       1:0x20c5018       0.0   0.0   0.0   1      0.0   0.0   0.0   32        32      90       90     1775     1775
6          18:01:59  Admin      2:0xc6018         0.4   0.4   0.0   1      0.0   0.0   0.0   2479      2479    182      22     5245     655
7          18:07:13  CKPTINTVL  2:0x776018        0.2   0.2   0.0   0      0.0   0.0   0.0   507       507     382      1      1712     5
8          18:17:13  CKPTINTVL  2:0x778018        0.0   0.0   0.0   0      0.0   0.0   0.0   1         1       26       0      2        0
9          18:27:14  CKPTINTVL  2:0x77f018        0.0   0.0   0.0   0      0.0   0.0   0.0   7         7       14       0      7        0
10         18:32:14  CKPTINTVL  2:0x781018        0.1   0.0   0.0   0      0.0   0.0   0.0   1         1       25       0      2        0

Max Plog       Max Llog       Max Dskflush   Avg Dskflush   Avg Dirty      Blocked
pages/sec      pages/sec      Time           pages/sec      pages/sec      Time
10240          1280           0              517            63             0

Based on the current workload, the physical log might be too small
to accommodate the time it takes to flush the buffer pool during
checkpoint processing.  The server might block transactions during checkpoints.
If the server blocks transactions, increase the physical log size to
at least 716800 KB.

For what I'm doing, that's ridiculous!  The information I see in that morass above does not indicate any issue that might cause a problem, if I understood Art's explanation to ABeMie in 2020.  I do plan to move all the logs (and increase the size of logical logs) into another DBspace later but I still think 716MB is kinda overkill, even if I do run a minor application.

At this time, onstat -d shows ROOTDBS over 57% free

What other ONCONFIG parameter[s] can I tweak to get rid of this scare tactic?  Or just ignore it?

Thanks for ideas, folks.