# Is InfluxDB fast enough for this? **URL:** \ **Category:** InfluxDB 2\ **Created:** [July 21, 2024, 2:38pm UTC](https://community.influxdata.com/t/is-influxdb-fast-enough-for-this/35026 "2024-07-21T14:38:35Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Yonatan](https://avatars.discourse-cdn.com/v4/letter/y/eb9ed0/32.png) [@Yonatan](https://community.influxdata.com/u/Yonatan)\ **Post date:** [July 21, 2024, 2:38pm UTC](https://community.influxdata.com/t/is-influxdb-fast-enough-for-this/35026/1 "2024-07-21T14:38:35Z")
Hi all, I’m new to InfluxDB I’ve recently installed InfluxDB on a local server (Ubuntu 24.04, Core i5 8500, 16GB RAM) to collect robot telemetry and create a dashboard from it, and it feels like I’m running into a speed ceiling. I’m writing ~450 data points (3 integer fields per point) per second, and even though the dashboard is refreshing once per second, the new data does not seem to be showing up at all. The graph just ends, despite the fact that my Python is continuously writing new data. I also have a gauge for battery %, and the number on it is significantly outdated. Looking at load on the server in btop, CPU usage seems near zero, disk I/O is at 2-4MB/s, network I/O is similarly near idle. So what is going on here? Why does InfluxDB seem to discard most of my data? For my query, I’m doing this: ```auto from(bucket: "RobotTelemetry") |> range(start: v.timeRangeStart, stop: v.timeRangeStop) |> filter(fn: (r) => r["_measurement"] == "power") |> filter(fn: (r) => r["_field"] == "current") |> filter(fn: (r) => r["robot_name"] == "Albert") ``` I specifically omitted the averaging/aggregation since it was hiding short peaks (current spikes can be 0.5s, so a 10s window just gets in the way) Are my expectations of InfluxDB unreasonable? Or am I doing something wrong? ---
**Author:** ![scott](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/scott/32/16492_2.png) [@scott](https://community.influxdata.com/u/scott)\ **Post date:** [July 22, 2024, 9:41pm UTC](https://community.influxdata.com/t/is-influxdb-fast-enough-for-this/35026/2 "2024-07-22T21:41:55Z")
@Yonatan This doesn’t seem like a super heavy write workload. How are you writing the data? Just through a Python script? Telegraf? Is there anything in the logs to suggest that writes are being rejected? ---
**Author:** ![Yonatan](https://avatars.discourse-cdn.com/v4/letter/y/eb9ed0/32.png) [@Yonatan](https://community.influxdata.com/u/Yonatan)\ **Post date:** [July 23, 2024, 6:54am UTC](https://community.influxdata.com/t/is-influxdb-fast-enough-for-this/35026/3 "2024-07-23T06:54:30Z")
I’m writing using the influxdb-python library, I’m creating a point with the data and publishing it using `WriteApi.write(...)` I checked the logs using docker logs using `docker logs --follow influxdb` and I don’t see anything being printed out while running all the writes ---
**Author:** ![scott](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/scott/32/16492_2.png) [@scott](https://community.influxdata.com/u/scott)\ **Post date:** [July 23, 2024, 2:15pm UTC](https://community.influxdata.com/t/is-influxdb-fast-enough-for-this/35026/4 "2024-07-23T14:15:18Z")
@Yonatan So do the writes never actually get written or are they delayed? ---
**Author:** ![Yonatan](https://avatars.discourse-cdn.com/v4/letter/y/eb9ed0/32.png) [@Yonatan](https://community.influxdata.com/u/Yonatan)\ **Post date:** [July 24, 2024, 9:12am UTC](https://community.influxdata.com/t/is-influxdb-fast-enough-for-this/35026/5 "2024-07-24T09:12:42Z")
@scott I wrote a burst of data at a high speed for around a minute, when starting to write, 4 seconds of data showed up, and since then nothing more. It has been ~20 minutes and no new data has arrived. ---
**Author:** ![scott](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/scott/32/16492_2.png) [@scott](https://community.influxdata.com/u/scott)\ **Post date:** [July 24, 2024, 1:14pm UTC](https://community.influxdata.com/t/is-influxdb-fast-enough-for-this/35026/6 "2024-07-24T13:14:07Z")
Interesting. And nothing in the logs around the time that writes stop landing? I’m curious, is it bucket-specific? If you write to a different bucket, do the writes work? What about just a straight API call rather than using the Python client. For example, if you create a new bucket and try to write data with a cURL request: ```sh curl --request POST \ "http://localhost:8086/api/v2/write?org=&bucket=&precision=ns" \ --header "Authorization: Token " \ --header "Content-Type: text/plain; charset=utf-8" \ --header "Accept: application/json" \ --data-binary ' airSensors,sensor_id=TLM0201 temperature=73.97038159354763,humidity=35.23103248356096,co=0.48445310567793615 1721826812564960000 airSensors,sensor_id=TLM0202 temperature=75.30007505999716,humidity=35.651929918691714,co=0.5141876544505826 1721826815811478000 ' ``` Does the write succeed? Do you get any errors back? ---
**Author:** ![Yonatan](https://avatars.discourse-cdn.com/v4/letter/y/eb9ed0/32.png) [@Yonatan](https://community.influxdata.com/u/Yonatan)\ **Post date:** [July 24, 2024, 2:01pm UTC](https://community.influxdata.com/t/is-influxdb-fast-enough-for-this/35026/7 "2024-07-24T14:01:07Z")
I tried running your command on a test bucket 6 times while running the robot, looks like all 6 went through while the data the robot sent was showing the same behavior. ---
**Author:** ![scott](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/scott/32/16492_2.png) [@scott](https://community.influxdata.com/u/scott)\ **Post date:** [July 24, 2024, 2:49pm UTC](https://community.influxdata.com/t/is-influxdb-fast-enough-for-this/35026/8 "2024-07-24T14:49:53Z")
This makes me think something might be failing client side. Anything in your Python logs? ---
**Author:** ![Yonatan](https://avatars.discourse-cdn.com/v4/letter/y/eb9ed0/32.png) [@Yonatan](https://community.influxdata.com/u/Yonatan)\ **Post date:** [July 25, 2024, 6:29am UTC](https://community.influxdata.com/t/is-influxdb-fast-enough-for-this/35026/9 "2024-07-25T06:29:24Z")
I’m not seeing anything in the Python output. Note that I’m using `write_options=ASYNCHRONOUS`, could async writes drop silently if there are too many for the client to handle? ---
**Author:** ![scott](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/scott/32/16492_2.png) [@scott](https://community.influxdata.com/u/scott)\ **Post date:** [July 25, 2024, 2:17pm UTC](https://community.influxdata.com/t/is-influxdb-fast-enough-for-this/35026/10 "2024-07-25T14:17:28Z")
> [@Yonatan](#): > > could async writes drop silently if there are too many for the client to handle? I’m not sure. I’ve never personally seen this behavior. You might consider creating an issue on the Python client repository.