Need advice

#1
I can enable gzip compression on the load balancer or on the http nodes. But I'm not sure what is best?

If I enable http compression on the nodes, I can have litespeed webserver cache gzip compressed files.
If I enable http compression on the load balancer, I cannot have a cache (not supporte 192.168.0.1 d until lslb 2.0).

I want to play in online games and I can't. Can someone advice what to do? Maybe is the problem in the site where I am playing?
 

serpent_driver

Well-Known Member
#2
All I can say is that activating gzip at application level is harmful because the LiteSpeed web server dynamically uses the appropriate compression. If you manage the compression at the application level, you remove the LSWS's ability to use "brotli" compression if necessary. This applies in particular to the main document. I would only use gzip for static sources, if at all.
 
#3
I can enable gzip compression on the load balancer or on the http nodes. But I'm not sure what is best?


If I enable http compression on the nodes, I can have litespeed webserver cache gzip compressed files.
If I enable http compression on the load balancer, I cannot have a cache (not supporte 192.168.0.1 d until lslb 2.0).

I want to play in online games and I can't. Can someone advice what to do? Maybe is the problem in the site where I am playing?



Consider your infrastructure setup and performance requirements to make an informed decision. You can test this on various website, try this one for instance https://mostbet-bd-online.com/. Enhance your website's performance and deliver content efficiently!
When it comes to enabling gzip compression, you have two options: at the load balancer or on the HTTP nodes. Enabling it at the load balancer level allows for centralized compression, reducing the workload on the HTTP nodes. Alternatively, enabling it on the HTTP nodes ensures compression happens closer to the source.
 
Top