Hi, openGauss team and guys in community.

We are very happy that we can get a chance to contribute some enhancement proposals to openGauss community. openGauss is a fast grown-up community and database. So we are eager to involve and work with u guys.

Via the in-depth study from `mysqlonarm` (gitee id) in our team, we found some interesting stuff in openGauss, tried the best to provide the solution and coding.

Such as  https://gitee.com/opengauss/openGauss-server/issues?assignee_id=&author_...

There are 4 issues we had been raised in openGauss. Most of them brings the benifits towards the performance. For example, 

1. Suggest for incremental checkpoint in read-only workload. https://gitee.com/opengauss/openGauss-server/issues/I50EYL?from=project-issu...

2. This is a global counter optimization, if you are interested, please see the details in issue. https://gitee.com/opengauss/openGauss-server/issues/I53QUI?from=project-issu...

3. This one has potential optimize openGauss select workload in range to 5-13%. https://gitee.com/opengauss/openGauss-server/issues/I51KOD?from=project-issu...

4. This one helps improve the logic to add free buffers as part of incremental checkpoint, via our testing and apply the code in issue, it shows a wide range gain. (5-200%) for read workload, (50-100%) for write workload. https://gitee.com/opengauss/openGauss-server/issues/I56OAW?from=project-issu...

All of aboves have potential work and worth to learn/test more for openGauss, we think those would make openGauss bettter sooner or later. We will try best to explore and contribute what we found in performance aspects. If you are interested in our improvement for openGauss, free feel to contact or discuss with us via email in openGauss ML.

Regards!