Closed m1sta closed 10 years ago
shortly I'll write a testing script (we have one internally at Grokker) and add it to the repo comparing this with https://github.com/medikoo/es6-map and bare objects for memory and time.
you can run tests/comparison.js to see the cpu difference between bare objects, es6-map and hashtable/es6-map. Spoiler alert hashtable/es6-map is almost as fast as bare objects. I'll add memory usage to it as well and we'll see that hashtable/es6-map is should be better than bare objects there (since the data is stored outside of node in c++ land).
It'd be great to see a couple of simple performance or scalability metrics to help understand the value of this module.