Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

staking TendermintUpdate Store should be in a transient store #1013

Closed
rigelrozanski opened this issue May 16, 2018 · 10 comments · Fixed by #2310
Closed

staking TendermintUpdate Store should be in a transient store #1013

rigelrozanski opened this issue May 16, 2018 · 10 comments · Fixed by #2310
Assignees

Comments

@rigelrozanski
Copy link
Contributor

Tendermint updates will only ever last within a block

** Verify that this may already be happening with caching the existing store implementation?

@cwgoes
Copy link
Contributor

cwgoes commented May 30, 2018

I wonder if we should consider this when charging for gas (somehow)?

At the moment we'll charge for storage reads/writes irrespective of whether they actually map to real disk reads/writes.

@rigelrozanski
Copy link
Contributor Author

I don't think it's a problem - we should just have a transient store which is charged at a lower rate (or not at all?)

@cwgoes
Copy link
Contributor

cwgoes commented May 31, 2018

I don't think it's a problem - we should just have a transient store which is charged at a lower rate (or not at all?)

Agreed, that's what I mean.

@ebuchman
Copy link
Member

From discussion, this is only used as a cache store so never written to disk. Closing for #1288

@rigelrozanski
Copy link
Contributor Author

not closed? it would be good to make this more obvious as a developer that this only ever lasts in the cache - right now the process train looks the same

Maybe we could introduce store writes that automatically clear at the end of the block, and make it clear when you're writing to this store that this is what happens

@cwgoes
Copy link
Contributor

cwgoes commented Jun 20, 2018

Need to make sure implementation would be clean, but I think we could have an option to mount a substore as "transient", and update CacheMultiStore to not write transient stores on .Write().

@ebuchman
Copy link
Member

Closed for #1326 and #1288

@rigelrozanski
Copy link
Contributor Author

Can't see where this has been updated in the codebase? reopening

@rigelrozanski rigelrozanski reopened this Sep 11, 2018
@rigelrozanski
Copy link
Contributor Author

https://github.com/cosmos/cosmos-sdk/pull/1481/files doesn't effect anything in x/staking

@rigelrozanski rigelrozanski self-assigned this Sep 11, 2018
@rigelrozanski
Copy link
Contributor Author

ON this one now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants