Greenstand/treetracker-query-api

Performance: optimize this API

Open

#219 opened on Oct 2, 2022

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)TypeScript (65 forks)auto 404
good first issuepostgresql

Repository metrics

Stars
 (17 stars)
PR merge metrics
 (PR metrics pending)

Description

url: https://prod-k8s.treetracker.org/query/species?planter_id=3024&limit=20&offset=0 took: 2658ms, this might be the same with https://github.com/Greenstand/treetracker-query-api/issues/216 but it's using a different filter(planter), so please also check the code Please find the responding router in the repo, and test it locally, note, local env is connecting to dev database, it might be faster than prod because fewer data.

Contributor guide

Research direction
Find the router handling the species endpoint with planter id filter, run it locally, profile the query to identify slow parts (e.g., database query or response serialization), and compare with the similar issue #216.
Tech stack
typescript
Domain
backend
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60