aymanhs72

5 ms·

1. 1.▲
   Jeeves: A minimal systemd TUI written in Go for lightweight hardware(github.com)

   3 points by aymanhs72 3mo ago|0 comments
2. 2.▲
   by aymanhs72 4mo ago

   I have used VM for a while and for my use case it was way better than influxdb. VM process takes 70 to 100Mb memory on my system. Not bad, but not great. NanoTDB takes just about 10 to 20Mb, and that does include the dashboard. NanoTDB
3. 3.▲
   by aymanhs72 4mo ago

   New Release out. Docs updated. Check it out
4. 4.▲
   by aymanhs72 4mo ago

   Thanks for the reply and explanation. I added rollups to the readme file too
5. 5.▲
   by aymanhs72 4mo ago

   I expect queries to be mostly around a single or few sensors around date range. There is no index but the files for live readings are daily based, and reading single day file is extremely fast. Rollups are also supported and act like norm
6. 6.▲
   by aymanhs72 4mo ago

   I already had that experience of some bad data and 85c degrees getting into my temperature sensor readings. BTW 85c just means it's invalid. So I do need to delete the bad data. The way it can be done now is to just export, filter a
7. 7.▲
   by aymanhs72 4mo ago

   Sorry being late. Rollups were only pushed recently, as I thought about them for a long time until it finally clicked. This is main advantage over straight log files. Another things is that it is designed to be extremely efficient with SD
8. 8.▲
   NanoTDB – Golang Append-Only Time Series DB(github.com)

   57 points by aymanhs72 4mo ago|20 comments