Skip to content

shouldUseEVM could be slightly optimized #952

@technicallyty

Description

@technicallyty

shoudlUseEVM function (mempool/iterator.go:142) calls:

	nextEVMTx, evmFee := i.getNextEVMTx()
	nextCosmosTx, cosmosFee := i.getNextCosmosTx()

however, one of it's callers, getPreferredTransaction, already has these variables loaded. another one of it's callers: advanceCurrentIterator doesn't.

i think we could make a small perf optimization by allowing getPreferredTransactionto pass in its values.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions