mirror of
https://github.com/mthenw/frontail.git
synced 2026-04-26 02:05:57 +03:00
[GH-ISSUE #37] Huge number of requests when following nginx logs #22
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/frontail#22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mkonecny on GitHub (Nov 25, 2014).
Original GitHub issue: https://github.com/mthenw/frontail/issues/37
Currently have an issue where if I follow nginx logs (which is reverse-proxying frontail), it seems like there is a positive-feedback effect happening where frontail polls after each new log event, which generates a nginx log event, which in turn causes frontail to poll again faster and faster, until I'm seeing well over 50 requests per second.
@mthenw commented on GitHub (Nov 25, 2014):
frontail uses socket.io underneath and, as you can see in your case, long polling is used. I'm not sure if it's wrong that there are so many requests? Why exactly is it a problem?
@mkonecny commented on GitHub (Nov 25, 2014):
I was thinking it may be useful to have a max request rate of 1-2 requests per second - assuming that each request can get all recent log entries, the end result would be similar to the current implementation, and a bit less taxing on the browser + server.
@mkonecny commented on GitHub (Nov 25, 2014):
Seems like this issue is resolved when I enable websockets in my nginx proxy. Thanks for the help, and great project.