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

[INLONG-111] Improve filter performance and increase the number of concurrent filters #111

Open
dockerzhang opened this issue Jul 28, 2021 · 3 comments

Comments

@dockerzhang
Copy link
Owner

At present, the number of concurrent filtering copies supported by the system is about 20 under 1k Topic. This function is very popular with users after it is launched. If we can increase the number of concurrent filtering consumption, we can greatly help the business.

1. Structured index storage: optimize the current index storage, for example, increase the structured index storage, which can be quickly retrieved through the index when in use to quickly locate the data; the increase in the index structure may make the write request slower, At the same time, it takes more time to check and restore the index when the system restarts

2. Cross-partition consumption ability: For data that is not sensitive to partitions, when filtering consumption, it should support cross-partition consumption instead of specifying partition consumption to improve the overall filtering consumption capacity, but there must also be a way to limit this Mechanism, the specific choice should be controlled by the user

JIRA link - [INLONG-111] created by gosonzhang
@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions
Copy link

github-actions bot commented Jul 9, 2022

This issue is stale because it has been open 60 days with no activity.

@github-actions github-actions bot added the stale label Jul 9, 2022
@github-actions
Copy link

github-actions bot commented Sep 7, 2022

This issue is stale because it has been open for 60 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant