You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Loading the GQL schemas for all indexed subgraphs can lead to high memory usage.
Since it's likely that even in the case where an indexer is indexing a large number of subgraphs, only a few are allocated, we can safely do this and save a lot of resources.
The text was updated successfully, but these errors were encountered:
BREAKING CHANGE: autoagora-processor needs to communicate with the
indexer-agent API (--indexer-agent-mgmt-endpoint) instead of
graph-node's PG DB (--graph-postgres-... args are gone).
Fixes#33
Signed-off-by: Alexis Asseman <[email protected]>
BREAKING CHANGE: autoagora-processor needs to communicate with the
indexer-agent API (--indexer-agent-mgmt-endpoint) instead of
graph-node's PG DB (--graph-postgres-... args are gone).
Fixes#33
Signed-off-by: Alexis Asseman <[email protected]>
Loading the GQL schemas for all indexed subgraphs can lead to high memory usage.
Since it's likely that even in the case where an indexer is indexing a large number of subgraphs, only a few are allocated, we can safely do this and save a lot of resources.
The text was updated successfully, but these errors were encountered: