Question BlobAsset or persistent NativeHashMap for config

I create many persistent NativeHashMap for static config.Just now,I realized BlobAsset is a official config solution and I compared performace between them.

In BlobAsset test,I stored BlobAssetReference that refers to only one config in component and access config by this component.
In NativeHashMap test,I stored configId in component and access config by NativeHashMap.

How ever,persistent NativeHashMap is much better in my test.(100+ Ticks in BlobAsset test and 0 Tick in NativeHashMap one).
It's a correct result or I just use BlobAsset in a wrong way?

 

I think if you are using blob asset store, you introduce additional overhead. Even tho, should be very tiny. You not only need to check for hash, but also fetch reference to the hashmap from blob asset. Plus you do that for every entity you process on.

While if you just pass hashmap to the job, you only need to access hash.

I don't think storing persistent native hash collections in blob asset, is right approach. But I can see, why it may be chosen this way.

 

I didn't store whole collections in BlobAsset,just only one.Each config has one BlobAsset.Poor English so I maybe confused you.