plor
commented
2 years ago This is probably more of an Epic in that there should be a task per job to identify what can be changed with discussions around the impact that will have. Add additional context or break up into tasks as necessary.
Query reduction
The jobs that run are hitting subgraph quite often and some jobs may not be needed and can be deprecated, while some jobs can reduce frequency or otherwise optimize. Since the cost of the graph is per query, it is important to limit the number of calls we make to our subgraph to the necessary ones that we can sustainably maintain.