Skip to content

performance: consider not using proxies for normal properties/methods #316

Description

@maltemoeser

Currently (on v0.6) accessing properties and methods of Python objects involves a function call to the corresponding proxy object (._self_proxy), which incurs a performance overhead that becomes significant for large numbers of individual objects. (e.g., [tx.fee for block in chain for tx in block] instead of chain.blocks.txes.fee). However, not all analyses may be doable using the proxy interface. We should consider whether we can use traditional properties and methods for these objects.

Related: #295, #311

Metadata

Metadata

Assignees

Labels

performancepythonIssue related to the Python interface

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions