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

[improve] Reuse the internal writer/reader under the same system topic #22087

Closed
1 of 2 tasks
poorbarcode opened this issue Feb 21, 2024 · 0 comments · Fixed by #22099
Closed
1 of 2 tasks

[improve] Reuse the internal writer/reader under the same system topic #22087

poorbarcode opened this issue Feb 21, 2024 · 0 comments · Fixed by #22099
Assignees

Comments

@poorbarcode
Copy link
Contributor

Search before asking

  • I searched in the issues and found nothing similar.

Motivation

So far, Pulsar creates an internal producer to send the Pulsar Event and close it after it is sent immediately.

The following Profile was captured when doing much topic creation and deletion.

image

Screenshot 2024-02-21 at 14 19 30

Solution

We can reuse the same writer/reader to improve the performance.

Alternatives

No response

Anything else?

No response

Are you willing to submit a PR?

  • I'm willing to submit a PR!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants