No, there is no any log and metrics suggestions and as i told earlier — this
place can`t became a bottleneck, if you have any performance problems —
describe them somehow wider and interesting reading here [1]
[1]
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood
>Thanks Zhenya.
>
>Is there any logging or metrics that would indicate if there was value
>increasing the size of this pool?
>
>
>On Fri, 2 Sep 2022 at 8:20 PM, Zhenya Stanilovsky via user <
>user@ignite.apache.org > wrote:
>>Hi Raymond
>>
>>checkpoint threads is responsible for dumping modified pages, so you may
>>consider it as io bound only operation and pool size is amount of disc
>>writing workers.
>>I think that default is enough and no need for raising it, but it also up to
>>you.
>>
>>>Hi,
>>>
>>>I am looking at our configuration of the Ignite checkpointing system to
>>>ensure we have it tuned correctly.
>>>
>>>There is a checkpointing thread pool defined, which defaults to 4 threads in
>>>size. I have not been able to find much of a discussion on when/how this
>>>pool size should be changed to reflect the node size Ignite is running on.
>>>
>>>In our case, we are running 16 core servers with 128 GB RAM with persistence
>>>on an NFS storage layer.
>>>
>>>Given the number of cores, and the relative latency of NFS compared to local
>>>SSD, is 4 checkpointing threads appropriate, or are we likely to see better
>>>performance if we increased it to 8 (or more)?
>>>
>>>If there is a discussion related to this a pointer to it would be good (it's
>>>not really covered in the performance tuning section).
>>>
>>>Thanks,
>>>Raymond.
>>> --
>>>
>>>Raymond Wilson
>>>Trimble Distinguished Engineer, Civil Construction Software (CCS)
>>>11 Birmingham Drive | Christchurch, New Zealand
>>>raymond_wil...@trimble.com
>>>
>>>
>>
>>
>>
>>
