This message was deleted.

it's good that the proposed tunable unblocks someone. but, imo we do have too many tunables for people to think about and it's a bummer to see that become more severe by adding one more 🙂 ideally i'd like to also include a nice writeup in the docs so users can determine a) when the tunable should be used b) what are reasonable values to set it to c) what drawbacks may occur by using the tunable for this one i guess the drawback [c] is that there would be increased memory usage, and so task heaps and max direct memory may need to be raised. the other nice thing about including [a] + [b] + [c] is that it provides a path for us to make the tunable self-tuning [with a dynamic value rather than static default]— which is ideal

I will try to cover these points in the documentation