Open bergundy opened 2 years ago
Do we actually want to do this? 128MiB seems extremely large and I'd start to worry about fairness issues between workflows/activities in the same worker.
I must admit that I have no recollection of why we did this, but it’s the behavior in both Go and Java now.
I think we just matched Java. It will get rejected by server-side limits anyways usually, but that is exposed as a config and this is not so it's set high enough not to be hit hopefully I guess.
To fix my statement above, server limit only applies to requests I think, but server response (e.g. a large page of history) can be large.
SDK checklist
Add a test that confirms this in
sdk-feature
repo