Hi Kyriakos, have a look at https://github.com/icing/mod_h2/releases/tag/v1.8.6
That version flushes when at least 2 TLS records are ready to send. Also, frame sizes are now aligned to TLS record sizes. So they are influenced by the H2TLSWarmUpSize and H2TLSCoolDownSecs settings. Additionally, and highly experimental, I added H2TLSFlushCount to configure the number of records to flush. You may play around with it (default is 2) in your scenarios. I hope that this reduces buffering and makes the server more (another word for agile, pls) to stream changes. Please let me know if that had any effect on your tests. Thanks, Stefan > Am 29.12.2016 um 12:40 schrieb Kyriakos Zarifis <kyr.zari...@gmail.com>: > > That means the images should get a minim of ~30% of the available bandwidth > as long as they have data. My reading. > > Right. Makes sense. Stefan Eissing <green/>bytes GmbH Hafenstrasse 16 48155 Münster www.greenbytes.de
