https://bz.apache.org/bugzilla/show_bug.cgi?id=65402
--- Comment #50 from Florian Meister <f...@sfs.com> --- (In reply to Stefan Eissing from comment #49) > I see 37 h2 worker busy at the time requests '66-289' to '66-295' arrive and > that is the maximum in your sever configuration. The processing can only > start when a worker becomes available again. > > You can mitigate that by an increased `H2MaxWorkers` configuration. > > The question is what usage your anticipate on that server when you take it > live. Increasing numbers of users with these SSE request will eventually > exhaust whatever worker limit you configure. > > Question: can you reduce the 30 seconds update time on the SSE generators? We have eliminated more or less all request cancellations when navigating through the page - so it's much better now even without your fix. Yes that would be possible. Maybe we take that approach. The problem is that we have one event-source which is transporting (potentially) a pretty big amount of data. If we reduce the interval it would increase the load and the traffic. We are going to send increments via this events in the future - so this problem should also be fixed in the future. > > (The desired fix would be for apache to get rid of those workers directly > when the client resets the stream, but that is not easily achieved.) For my understanding: Is one H2Worker is processing exactly one request and while processing is not able to process other requests? If this is the case we would have to set H2MaxWorkers to a pretty big value. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
