-
Notifications
You must be signed in to change notification settings - Fork 33
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
R's byte compiler overhead #149
Labels
Comments
dselivanov
added a commit
that referenced
this issue
Jun 10, 2020
- disable jit within Rserve backend by default - try to recursively byte-compile global env by default
Several discoveries here
Recent changes in 3516e89 led to noticeable speedup when Fork overhead is ~1ms on my machine. |
Another speed up to R6 classes - https://github.com/duncantl/R6CompileNew |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue #146 brought interesting discovery.
@s-u I actually haven't check the R benchmark code from #146. I was pretty sure that the main issue was due to fork overhead (which was somewhat aligned with my benchmarks here).
However I've run your code and indeed the fork overhead is very small. And that pointed me to the real source of why things are pretty slow when keep-alive is disabled: R's byte compiler. The "issue" here is that it seems compile
.http.request
and functions which are used inside it during every invocation. And since each request is handled in a fresh fork, it compiles it every time which adds significant overhead. I was suspecting this and tried to mitigate it here, but it seems it is not enough.Consider following (pure Rserve) example:
Testing with disabled JIT and disabled
keep-alive
gives around 550 req/s
Testing with enabled JIT and disabled
keep-alive
gives around 25 req/s
@s-u do you have any ideas on how to mitigate this apart from disabling byte compiler? (I don't really have an idea on how R's byte compiler works)
The text was updated successfully, but these errors were encountered: