Allow opt out of time travel

[0xSkly]

For entities which have a lot of changes, like an exchange which changes on every swap, we have seen quite some slow down on query times against the database. Im not fully aware on how much impact the time travel feature (being able to query an entity at a specific block height) has but i'd imagine it's quite relevant when looking at the number of entries in some of those tables and the necessity to join on the block range.

Would it be completely against the spirit of the graph protocol to have a way to opt out of this feature and only store the latest entity? Kinda like the immutable entities, just that you can mutate them.

If this would result in some better query performance, i'd be worthwhile to omit the time travel in some cases and create our own aggregations maybe on a hourly basis which is more than granular enough for most of our use cases.

[github-actions]

Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.

[banianxd]

Option for mutate entity or not is awesome, have you figured out any way to mutate entities?

[fordN]

Pruning allows this essentially!