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

Fix StreamIdGenerator performance (see comments inside) #3

Open
KowalczykBartek opened this issue Jun 19, 2018 · 0 comments
Open

Fix StreamIdGenerator performance (see comments inside) #3

KowalczykBartek opened this issue Jun 19, 2018 · 0 comments
Labels
bug Something isn't working

Comments

@KowalczykBartek
Copy link
Contributor

see comment

he c++ clients often have ~30K pending requests to backends - no big deal.

You can have code to check if session has been released, but you can also just explicitly document it.

Say, you can at-most be 65K requests away. It will fail otherwise.

we can have a roaring bitmap since this sessions have really nice properties of effectively monotinic increasing sequences mostly that tells the user if the request id is inuse.

IMO - we can defer that as long as we document it. it is rare - though has happened - on failure - for one client to have 65K outstanding reqs.
@KowalczykBartek KowalczykBartek added the bug Something isn't working label Jun 19, 2018
@KowalczykBartek KowalczykBartek changed the title Fix StreamIdGenerator (see comments inside) Fix StreamIdGenerator performance (see comments inside) Jun 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant