We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Windows has a serious performance problem with large notification buffers, documented here:
https://randomascii.wordpress.com/2018/04/17/making-windows-slower-part-1-file-access
However a comment on that blog post claims that this performance problem has been fixed, based on the reporting in the blog post:
https://randomascii.wordpress.com/2018/04/17/making-windows-slower-part-1-file-access/#comment-48064
So, a future version of VsChromium could/should conditionally use large notification buffers.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Windows has a serious performance problem with large notification buffers, documented here:
https://randomascii.wordpress.com/2018/04/17/making-windows-slower-part-1-file-access
However a comment on that blog post claims that this performance problem has been fixed, based on the reporting in the blog post:
https://randomascii.wordpress.com/2018/04/17/making-windows-slower-part-1-file-access/#comment-48064
So, a future version of VsChromium could/should conditionally use large notification buffers.
The text was updated successfully, but these errors were encountered: