-
Notifications
You must be signed in to change notification settings - Fork 651
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ingress makes videos from Frigate download 4 times slower #5209
Comments
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Hm, so things did improve a bit. This is most likely due to faster aiohttp WS processing with the 3.10.x releases. I guess a slight slowdown is kinda expected since we add some proxying with ingress. But the amount of slowdown does seem a bit excessive. Especially since this can be rather big transfers. @bdraco do you have thoughts on this? |
aiohttp isn't well suited to be a proxy for high volume data. It simply isn't optimized for this use case. Someone would need to spend a few days/weeks optimizing it to improve the throughput, but even than it will always be slower since there is a cost to proxy the data. It will probably get a little bit better over time but a major improvement isn't likely without someone spending the time to optimize for this use case. |
Hm, long term, maybe it would be a better solution to setup a Nginx or something to handle ingress? 🤔 |
Yes that would be a lot faster solution for sure |
There is also a chance the |
Also on the core side we use https://github.com/home-assistant/core/blob/68d6f1c1aab2cf80b51191f2c617c9a7fc81aa7a/homeassistant/components/hassio/ingress.py#L212 on supervisor its 4096 chunks supervisor/supervisor/api/ingress.py Line 281 in 91a8fae
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Still happening. Still interested. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Still happening. Still interested. |
Describe the issue you are experiencing
I noticed when playing recorded videos from Frigate via the Frigate UI, it was taking a good while to load each clip (8MB clips in 3s). After some debugging with Frigate devs on Discord, we figured out it was Ingress fault.
When accessing Frigate UI directly with its port, the same clips download 4 times faster (8MB clips in 700ms). This confirmed it wasn't a Frigate issue but a HA Ingress issue.
See here the comparison:
I use HAOS, and use an internal M2 SSD. Recordings are stored there, same as HAOS. Host is connected via Eth, and the laptop I'm using to access is too using Eth.
Not certain when this started. I don't think it was due to recent updates (either Frigate or HA). I just committed to ask about the issue now.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Steps to reproduce the issue
ts
files.Anything in the Supervisor logs that might be useful for us?
The text was updated successfully, but these errors were encountered: