When utilizing the new Array(size) constructor, it appears that if the value of size is not constant, certain browsers (such as Chrome) may create a sparse array, leading to slower access times compared to using the default constructor. You can see this performance difference illustrated here.
This behavior is contrary to my intentions: I aim to pre-allocate an array of specified size in order to prevent dynamic re-allocation and ultimately enhance performance. Is there a way to achieve this desired outcome?
Please be aware that the focus of this question does not pertain to the ambiguity associated with the new Array(size) constructor. For further insights on that matter, you can refer to my recommendation shared here.