sofastack/sofa-registry

Issue of high CPU usage by the meta leader

Closed this issue · 4 comments

cause by Poor performance fasterxml jackson & No cleanup mechanism on operator.node blacklist

image

after clean up

image

i think we can maintain a version and operator object in memory, skip deserialize when version in memory equals to version in db.

sounds kind of like a distributed configuration center
Comparing with Nacos, config center is also a considerable functionality for SOFARegistry

Absolutely right.

Moreover, When dealing with more than 100+ data points, the benchmark results indicate that Gson outperforms Jackson by a factor of 5 in terms of performance. replace Jackson with Gson when deserialize operator.node blacklist

sounds like a major project.