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
The benchmarked weights currently only contain reads and writes. With state version 1, there is a big over-estimation when deleting keys since it will still consider the MEL bound for those.
Need to split it up into READS/WRITES/DELETES and then limit the deletion PoV weight of the value to 32.
I did not check the code recently on how the backend would know that something is deleted instead of written, but probably possibly to find out.
The text was updated successfully, but these errors were encountered:
The benchmarked weights currently only contain reads and writes. With state version 1, there is a big over-estimation when deleting keys since it will still consider the MEL bound for those.
Need to split it up into READS/WRITES/DELETES and then limit the deletion PoV weight of the value to 32.
I did not check the code recently on how the backend would know that something is deleted instead of written, but probably possibly to find out.
The text was updated successfully, but these errors were encountered: