Allocate a big buffer enough to hold all MD5 strings, instead of allocating it on heap one by one.
Also materialize all MD5 strings if the full profile is being read since all these strings are generated anyways.
Improved around 3% speed on loading an ExtBinary profile with 1GB total size/10 million names.
This refactoring takes precendence over the refactoring of using MD5 as key
Can we reduce the size using hex encoding?