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

RS_CACHE_MVCC_MAX_DEPTH needs a better heuristic #338

Open
jamadden opened this issue Aug 28, 2019 · 1 comment
Open

RS_CACHE_MVCC_MAX_DEPTH needs a better heuristic #338

jamadden opened this issue Aug 28, 2019 · 1 comment

Comments

@jamadden
Copy link
Member

It's a very simple value right now, that doesn't take into effect transactions per second or transaction size in an environment.

https://github.com/zodb/relstorage/blob/master/src/relstorage/cache/mvcc.py#L527

@jamadden
Copy link
Member Author

Adding some logging might help understand how production environments are reacting with the current settings.

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