You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After yesterday's community discussion and #318, I am trying to understand how Metadata implementation is stored in Kura, compared to Store assets.
Does each change in metadata create some record in the blockchain with an update, making the read performance similar and reducing it in cases of large Metadata contents?
The approach to performance here is worth documenting to explain to the users when Store assets are preferable, at least in my opinion.
The text was updated successfully, but these errors were encountered:
As confirmed by @appetrosyan, both Store and metadata modifications are stored as blockchain records, thus the retrieval speed is only worse for metadata in certain cases.
After yesterday's community discussion and #318, I am trying to understand how Metadata implementation is stored in Kura, compared to
Store
assets.Does each change in metadata create some record in the blockchain with an update, making the read performance similar and reducing it in cases of large Metadata contents?
The approach to performance here is worth documenting to explain to the users when
Store
assets are preferable, at least in my opinion.The text was updated successfully, but these errors were encountered: