DBZ-7618 Prevent multiple calls to pu.maxTimestamp()

[samssh]

Invoking the pu.maxTimestamp() function within the handleRowModifications method, which is inside a loop in handleRowIterator, can lead to performance issues and significantly slow down the connector.

[samssh]

https://issues.redhat.com/browse/DBZ-7622

[github-actions]

Welcome as a new contributor to Debezium, @samssh. Reviewers, please add missing author name(s) and alias name(s) to the COPYRIGHT.txt and Aliases.txt respectively.

[jpechane]

@samssh Applied, thanks!

[Ficooooooo]

Invoking the pu.maxTimestamp() function within the handleRowModifications method, which is inside a loop in handleRowIterator, can lead to performance issues and significantly slow down the connector.

Hi @samssh, I've encountered with performance issue as well, and I've test performance of 2.5.3.Final, it seems like there is no difference on performance when reading the commit log files, did I use the wrong version or I need to change some configurations?

And based on your test, is the problem fixed?

[samssh]

Invoking the pu.maxTimestamp() function within the handleRowModifications method, which is inside a loop in handleRowIterator, can lead to performance issues and significantly slow down the connector.

Hi @samssh, I've encountered with performance issue as well, and I've test performance of 2.5.3.Final, it seems like there is no difference on performance when reading the commit log files, did I use the wrong version or I need to change some configurations?

And based on your test, is the problem fixed?

Hi @Ficooooooo. I answered your question here