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

Performance issue about websocket of CKB node #4489

Closed
Keith-CY opened this issue Jun 21, 2024 · 2 comments · Fixed by #4505
Closed

Performance issue about websocket of CKB node #4489

Keith-CY opened this issue Jun 21, 2024 · 2 comments · Fixed by #4505
Labels
t:bug Type: This doesn't seem right.

Comments

@Keith-CY
Copy link
Collaborator

Keith-CY commented Jun 21, 2024

Bug Report

Current Behavior

Recently we have done a test about fee rate estimation. During the test, numerous transactions(40k+) have been submitted onto the chain and the tx pool is full of pending transactions(30k+) according to the RPC get_raw_tx_pool.

Our app subscribes to the CKB node via WebSocket, and pending transactions are expected to be pushed to our end. However, only 3k transactions had been received during the test, and the rest were reached in blocks.

Here's our question, is there a limit on the number of transactions pushed by WebSocket?

Expected Behavior

Most/all pending transactions should be pushed via WebSocket.

Environment

  • CKB version: v0.116.1
  • Chain: testnet
  • Operating system: Ubuntu 18.0.6 LTS
  • Arch: X86_64
  • Installation: GitHub Release

Additional context/Screenshots

The original issue could be found at Magickbase/ckb-explorer-public-issues#704 and a question post could be found at https://talk.nervos.org/t/performance-issue-about-websocket-of-ckb-node/8248

After a brief inquiry, I was led to open a bug report here.

@Keith-CY Keith-CY added the t:bug Type: This doesn't seem right. label Jun 21, 2024
@zmcNotafraid
Copy link

@eval-exec
Copy link
Collaborator

How is your CPU performance?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t:bug Type: This doesn't seem right.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants