5 ms·
Yeah, every home IoT hub processes more messages than that with less thsn raspberri pi worth of compute
by ClumsyPilot 5y ago
Yeah, every home IoT hub processes more messages than that with less thsn raspberri pi worth of compute
- earleybird 5y agoI certainly appreciate the sentiment though I'm pretty sure I don't have the same reliability and uptime guarantees on my little Rpi3/MQTT/NodeRed/SQLite/ESP8266 home system :-) That said, it's been running for upwards of 4 years and accumulated an insane number of temperature readings inside and above heating vents (heat source is heat pump) SELECT count() as count FROM temperatures : msg : Object { _msgid: "421b3777.908118", topic: "SELECT count() as count FROM …", payload: 23278637 } Ok, I need therapy for my data hoarding - 23 million temp samples is not a good sign :-)
- brodouevencode 5y agoCurious as to why you aren’t tracking that with a time series database?
- earleybird 5y agoIt's hobby diversion so minimal effort is a factor. That and that SQL query comes back in seconds. The initial experimentation was with ESP8266's and the MQTT/NodeRed/SQLite played a supporting roll. My experience with SQLite is that it can take you a long ways before needing to look elsewhere.
- ClumsyPilot 5y agoThe IoT hubs are an embedded system, built with a minimal memory footprint and overhead, 512 mb of ram is typical, sometimes less. Here is an example: https://www.gl-inet.com/products/gl-s1300/ https://www.gl-inet.com/products/gl-s1300/ That means you can't have docker and different versions of Java, node and .Net all running in parallel. You run a single process and Sqlite is a library that allows SQL operations and database to be inbuilt. You 'budget' is like 100 mb of Ram, becauae other stuff has to run too. All the time-series databases I know are a large, memory hungry hippo, built for distributed compute/kubernetes. Just very different usecase. If one was built with minimalism in mind, then it could be used.