Simba-Avionic / Simba-Avionic/gs_web_app
Research better ways to query data from DB
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 3
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
This is a more of an open issue. We want to maximize efficiency of queries done to DB, especially because they are done on Raspberry Pi with limited computing power. Right now we ask db for points in 1 second intervals, so when we ask for 1hour of historic data it responds with 3600 points.
It was done that way because ON/OFF telemetry could be lost when larger intervals were to be used. But for normal temperature / pressure values I think we can make the interval larger and maybe use "mean" aggregation.
So overall, the task is to measure current time of query and try to lower it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or query entry point; start by locating where historical telemetry queries are assembled and run. Measure the current query time on the Raspberry Pi, then evaluate interval and aggregation changes for temperature and pressure while checking that ON/OFF telemetry is not lost. Done means a measured query-time improvement with the relevant telemetry behavior documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100