[VM] Analyze Cosmwasm ERC-20 contract load point about cosmwasm HOT 4 CLOSED

Compared to the cosmwasm-plus/cw-20 code, the following differences were identified.

Erc20 contract is stored directly in prefixed storage, and serialized by calling Uint128.u128().to_be_bytes().
However cw20 uses bucket and updates Uint128 directly.
The bucket uses the serialization of the type trait, and Uint128 serializes the base64 string according to the annotation.

Cosmwasm explains that the bucket type is helpful in removing boilerplate that occurs in frequent serialization/deserialization repetitions.

So, if you reduce the directly use of Uint128 types without casts and frequent serialization repetitions using buckets, I guess you will see a valid performance difference.

from cosmwasm.

I was changed on TODO to focus for analyzing the cache logic.

from cosmwasm.

@brew0722
Is this issue still needed? or should be closed?

from cosmwasm.

@whylee259 Although serialization that is executed to obtain the key value to be stored in storage is repeated every time, So there is an overhead.
However There seems to be no effective way to remove it.
(Buckets are just wrappers so they serialize the same. The above was my mistake.)

I'll close it.

from cosmwasm.