On 10/6/22 8:11 AM, Dr. Werner Fink wrote:
Hi,
Just to mention due to the extrem memory consumption during unicode tests
with enabled altenative array implementation the speed win is more then
equalised. That is the build system becomes unusable
The unicode test allocates a sparse array with a max index of 1879048270.
The standard implementation handles that just fine. The alternate
implementation just tries to allocate an array and exceeds the data size
limit long before it gets to the max. Depending on your resource limits
and your VM system, the system will keep grinding away trying to satisfy
those malloc requests.
That's the tradeoff: space vs speed.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
