Clarifying documentation - On async calls #176
nemosmithasf
started this conversation in
General
Replies: 1 comment 2 replies
-
Actually the worker code is generated the first time, and after that the code is cached but not the worker instance. This could be probably be changed to actually cache the worker instance to improve performance. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
if you call unzip ten times, the overhead only applies for the first call, but if you call unzip and zlib, they will each cause the 70ms delay.
Is this implying that we are reusing the workers if we call the same function consecutively, but we are re-instantiating workers if we call alternating functions? i.e. the function keeps track of worker types in the background?
Beta Was this translation helpful? Give feedback.
All reactions