Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitor with SDK v2 performs much worse under high TPS #1814

Closed
xin-hedera opened this issue Apr 5, 2021 · 0 comments · Fixed by #1816
Closed

Monitor with SDK v2 performs much worse under high TPS #1814

xin-hedera opened this issue Apr 5, 2021 · 0 comments · Fixed by #1816
Assignees
Labels
bug Type: Something isn't working monitor Area: Monitoring and dashboard P1 regression
Milestone

Comments

@xin-hedera
Copy link
Collaborator

Detailed Description
Monitor (>= 0.29.0) with SDK v2 can't reach target TPS in GKE with resource limit (cpu=1.75, memory=4G). With previous monitor, a single pod can reach and sustain 1500 TPS HCS messages.

Profiling reveals the new monitor has higher memory footprint, which causes more frequent GC pause, higher CPU usage, thus lower performance.

Actual Behavior

Expected Behavior
The new monitor with SDK v2 should perform as well as or better than old versions.

Environment:

Additional Context

@xin-hedera xin-hedera added bug Type: Something isn't working P1 regression monitor Area: Monitoring and dashboard labels Apr 5, 2021
@xin-hedera xin-hedera self-assigned this Apr 5, 2021
@steven-sheehy steven-sheehy added this to the Mirror 0.32.0 milestone Apr 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Type: Something isn't working monitor Area: Monitoring and dashboard P1 regression
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants