Best values for lgwin and lgblock? about brotli HOT 8 CLOSED

Basic formulae is max(24, min(10, log2(size)+0.5)), if memory itself is not a problem.
If memory is a limited resource, then lgwin should be lowered a bit, but for higher qualities, hashers might take more memory than ring-buffer, so cutting lgwin won't give a big win.

from brotli.

Does this solution make sense?

params.lgwin = 22;

for (int i = 10; i < 22; i++)
{
    if (encodedSize <= (1 << i))
    {
        params.lgwin = i;

        break;
    }
}

from brotli.

lgwin can be up to 24 in brotli, but the maximum you want to use depends on the capabilities of the client running the decoder. For the mobile web use it might be wise to avoid the levels 23 and 24, and possibly smart to stay at 19.

from brotli.

lgwin of 24 bit means more than 50 MB of memory usage.

the question is still active: does my code make sense, and wouldnt it be a good idea to add this functionality functionality to the param-class?

from brotli.

This could easily be added to BrotliCompressBuffer method, but impossible for streaming versions (as the data size is unknown).

So, if we add the logic that reduces window size to BrotliCompressBuffer, will it work for you?

from brotli.

Why not add the size as an optional parameter to BrotliParams() constructor?

from brotli.

It would look a little bit confusing and redundant - lgwin and lgblock already specify the expected use-case. Probably it can be done with some helper function that adjusts BrotliParams given the expected input size...

from brotli.

Yes, that would be good.
At least some formula on the documentation. I'm interested in knowing how can I limit the amount of memory used while decoding by tunning the encoding parameters,

from brotli.