Suggest an Idea

[RanLupovich]

While moving our use case to log stream we found out that there is hidden parameter that allows to disable compression while writing to internal log stream component while turning off the compression we see a very high increase in the throughput , we tried to understand with support what causing this difference between using compression on lowest ratio of 2 compared to turning it off , the support suggested that a feature request should be raised for tuning the more the compression of the log stream , thanks

02003938 — Koby Ariely (QlikTech)

23 November 2020 at 13:12

Actions for this Feed Item

Hi Ran,

Note: for some reason, this case was marked as closed. Not sure why. I am re-opening it now.

We did some additional discussions with R&D.

From what it looks like to us,  from product preceptive, the only thing that could be done is add a feature request to improve the compression process (there could be several options , for example, have compression be done in a separate thread than the processing the changes)

So right now, we can only see the following solutions: either finding some solution on the OS side , like file systems that support compression as we wrote in the previous comments, or request for a feature request to improve the compression process)

[Anonymous]

I would be interested in knowing this parameter is in disabling the compression feature of log stream, is it possible that can be shared?

[Shelley_Brennan]

@Anonymous  - If you open a support case they should be able to review your use case and then provide the instructions on disabling the compression parameter.  Thanks!

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.