[X] I checked the documentation and found no answer to my problem.
[X] I checked the existing issues to make sure my problem has not already been reported.
[X] I have read the code of conduct before creating this issue.
Expected Behavior
Getting transactions ordered by block height descending should be fast enough without having to include additional filters.
Current Behavior
Query goes through but seems to be clocking at around 46 seconds for the 20 latest transactions.
Including an offset does not seem to have a meaningful impact on the time.
Steps To Reproduce
Run this query on the fetch mainnet subquery ui.
query latestTransactions { transactions(first: 20, orderBy: TRANSACTIONS_BY_BLOCK_HEIGHT_DESC) { nodes { block { height } } } }
Jonathansumner
commented
1 year ago
Prerequisites
Expected Behavior
Getting transactions ordered by block height descending should be fast enough without having to include additional filters.
Current Behavior
Query goes through but seems to be clocking at around 46 seconds for the 20 latest transactions. Including an offset does not seem to have a meaningful impact on the time.
Steps To Reproduce
Run this query on the fetch mainnet subquery ui.
query latestTransactions { transactions(first: 20, orderBy: TRANSACTIONS_BY_BLOCK_HEIGHT_DESC) { nodes { block { height } } } }Context
No response
Failure Logs
No response