electerious/Ackee

Improve performance

Open

#146 opened on Aug 16, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (385 forks)github user discovery
help wanted

Repository metrics

Stars
 (4,667 stars)
PR merge metrics
 (PR metrics pending)

Description

The new dashboard in v2 requires multiple aggregations and can therefore take longer to load. It's worth to take a closer look at the aggregations and GraphQL resolvers as there might be a lot to improve when it comes to performance.

  • Check if it's possible to cache some data
  • Check if there's data that is fetched multiple times from the database during one request
  • Check why the recent aggregation is so slow
  • Improve performance of facts and other GraphQL resolvers

Contributor guide

Research direction
Analyze the GraphQL resolvers and database queries to identify N+1 issues, redundant fetches, and missing indexes. Consider caching strategies for aggregations.
Tech stack
javascriptnodejsgraphql
Domain
backendapianalytics
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Node.jsGraphQLSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50