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

Investigate performance of proposals with large bodies #1585

Closed
letmaik opened this issue Sep 8, 2020 · 1 comment
Closed

Investigate performance of proposals with large bodies #1585

letmaik opened this issue Sep 8, 2020 · 1 comment
Labels
2.0.x Short-term improvements to 2.0 bug
Milestone

Comments

@letmaik
Copy link
Member

letmaik commented Sep 8, 2020

In #1575 the request timeout was increased from 3s to 10s to avoid intermittent timeout failures caused by #1557.

3s should be enough to handle ~500KiB.

On top of that, in CI, timeouts were not happening in SGX, but in virtual enclaves and I wasn't able to reproduce them locally on a DC8 . A factor in this is that virtual enclave builds in CI don't run on DC8 but on D8S, which probably has different performance characteristics.

@letmaik letmaik added the bug label Sep 8, 2020
@achamayou achamayou added the 2.0.x Short-term improvements to 2.0 label May 23, 2022
@achamayou achamayou added the p2 label Jul 14, 2022
@shokouedamsr shokouedamsr added this to the 2.x milestone Jul 22, 2022
@achamayou
Copy link
Member

The virtual debug build is heavily instrumented (ASAN and UBSan), and current efforts for managed application runtime are directed at containerised handlers, rather than optimising the JS interpreter, so we are not going to look at this in the foreseeable future.

@achamayou achamayou closed this as not planned Won't fix, can't repro, duplicate, stale Aug 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.0.x Short-term improvements to 2.0 bug
Projects
None yet
Development

No branches or pull requests

3 participants