# Victoria Metrics to Node-RED
**URL:** https://discourse.nodered.org/t/victoria-metrics-to-node-red/86347
**Category:** General
**Tags:** database
**Created:** [11 March 2024 21:40 UTC](https://discourse.nodered.org/t/victoria-metrics-to-node-red/86347 "2024-03-11T21:40:43Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@davidz](https://discourse.nodered.org/u/davidz)
#### Post date: [11 March 2024 21:40 UTC](https://discourse.nodered.org/t/victoria-metrics-to-node-red/86347/1 "2024-03-11T21:40:43Z")
Have anybody used Victoria Metrics? Victoria Metrics seems to be much more efficient than InfluxDB, use less memory, and less data storage.
InfluxDB is releasing 3.0, which breaks the Flux query language again. InfluxDB 3.0 looks to address its memory and storage issue.
It looks like there is no Node-Red interface developed for Victoria Metrics at this moment.
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [11 March 2024 22:56 UTC](https://discourse.nodered.org/t/victoria-metrics-to-node-red/86347/2 "2024-03-11T22:56:25Z")
First time I've seen that. You could also look at TickTockDB
> [@Using TickTockDB (open source Time Series DataBase) on RPI 2 model B or RPI 3 and Node-red](https://discourse.nodered.org/t/using-ticktockdb-open-source-time-series-database-on-rpi-2-model-b-or-rpi-3-and-node-red/84873):
>
> I stumbled on Ticktockdb awhile ago and decided to try it as a replacement for Influx. After some starts and stops, I got it to install on a Rpi 2 Model B and it is running with no problems that I see. I have three sensors sending data (Temperature, Pressure and Humidity) via MQTT so I built a flow that gets the data, formats it and sends it to the ticktockdb. I also build a dashboard that graphs the data based on selectable criteria. Here are the instructions for installing ticktockdb: [TICKT…](https://discourse.nodered.org/uploads/short-url/qO1e7lHkQRlchvNGpLBFSoFa18b.pdf)
---
### Author:  [@davidz](https://discourse.nodered.org/u/davidz)
#### Post date: [12 March 2024 00:07 UTC](https://discourse.nodered.org/t/victoria-metrics-to-node-red/86347/3 "2024-03-12T00:07:24Z")
TickTockDB is still in its infantry stage. Victoria Metrics is much more mature, and has been around for a long time. At Github, It is 67 stars vs 10.5k stars.
Here is a discussion at HA on comparison of InfluxDB with Victoria Metrics:
> **[InfluxDB vs VictoriaMetrics](https://community.home-assistant.io/t/influxdb-vs-victoriametrics/453361/21?page=2)**
>
> …hard to say what the trend will be, but I consider VM a top contender and the logical choice for those who don’t want to deal with InfluxDB 2. fwiw, I’ve been running both side by side on a pi4 with no performance issues. as far as I can tell...
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [12 March 2024 10:31 UTC](https://discourse.nodered.org/t/victoria-metrics-to-node-red/86347/4 "2024-03-12T10:31:48Z")
Well if you are using HA and want to use VM and need help, you should ask on the HA forum.
I was just offering you a alternative that is working well. While there is no 'node' for TickTockDB one of the authors @ylin30 is on the forum and very helpful.
---
### Author:  [@davidz](https://discourse.nodered.org/u/davidz)
#### Post date: [12 March 2024 15:56 UTC](https://discourse.nodered.org/t/victoria-metrics-to-node-red/86347/5 "2024-03-12T15:56:51Z")
No we did not use HA. This has nothing to do with HA.
We use InfluxDB. But we are looking at alternative solution that is industrially proved reliable and efficient. We are looking for long-term industrial database solutions such as Victoria Metrics and TimeScale that could offer better performance.
Would love to hear what others think about this.
---
### Author:  [@ylin30](https://discourse.nodered.org/u/ylin30)
#### Post date: [12 March 2024 17:54 UTC](https://discourse.nodered.org/t/victoria-metrics-to-node-red/86347/6 "2024-03-12T17:54:15Z")
@zenofmud thanks for ur kind words.
@davidz Yes, TT is still in infantry (~5 yrs) and still actively being improved. Our goal is to make TT fastest and least resource required so it can run in low resource devices like PIs. You might want to check out [TT's early perf here](https://github.com/ytyou/ticktock/wiki/Performance-comparison:-InfluxDB,-TimescaleDB,-IoTDB,-TDEngine,-OpenTSDB-v.s.-TickTock). Also if you are switching from OpenTSDB, it's the best replacement.
If you're looking at mature solutions, you might want to check TDEngine besides VicMetrics. TDEngine has some limitations in schema and not as flexible as VicMetric. But both are much more lightweight than InfluxDB. VicMetric is pretty good in data compression so its storage size is even better than InfluxDB (so is its IO utilization).
I won't suggest TimeScaleDB due to its poor perf (since it is based on PostgreSQL). But if your perf requirement is not high and you care more about stability and security features, TimeScaleDB may be your choice. Recently it also claims to be vector DB (AI-related).
You're welcome to try TT. Any questions are welcome. Good luck!
---
### Author:  [@davidz](https://discourse.nodered.org/u/davidz)
#### Post date: [13 March 2024 22:26 UTC](https://discourse.nodered.org/t/victoria-metrics-to-node-red/86347/7 "2024-03-13T22:26:53Z")
@ylin30 Thanks much for the comments.
TimeScaleDB is from PostgreSQL ++, which is famous for industrial standard SQL.
But most likely, we will invest some effort on Victoria Metrics. It is crucial to have consistent design and high performance.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [11 June 2024 22:27 UTC](https://discourse.nodered.org/t/victoria-metrics-to-node-red/86347/8 "2024-06-11T22:27:42Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.