Improve Logs performance

[fedekunze]

Emitting tx logs decreased its performance due to #556 (see benchmarks).

Our tradeoff was decreasing the amount of state used in favor of this new approach, but we should come up with a new implementation that doesn't affect performance negatively.

cc @yihuang

[yihuang]

It's strange that emitting cosmos events could become a bottleneck, I'll have a look.

[yihuang]

There are two changes we did to tx logs handling:

• Change tx log storage from normal store to transient store
• Emit all the logs as events at the end of tx processing

The first step is the same as before, the second step can be considered as the counterpart of the storage flushing in the previous approach, but the storage flushing is not covered in the benchmark, while the event emitting is, so that might explain the difference.

[tomtau]

@JayT106 can this issue be closed after #587 or are there more performance improvements to be done?

[JayT106]

@fedekunze do you think any log issues in the latest codebase we need to improve?

[github-actions]

This issue is stale because it has been open 45 days with no activity. Remove Status: Stale label or comment or this will be closed in 7 days.

[yihuang]

This issue should be fixed by #729 too.

[github-actions]

This issue is stale because it has been open 45 days with no activity. Remove Status: Stale label or comment or this will be closed in 7 days.