Search results

CPU affinity only help when server has been pushed to the maximum. "RAM disk path" has default under /dev/shm , so, I doubt you will notice anything difference.

https://docs.litespeedtech.com/lsws/recaptcha/ let server to drop connection after a few failures.

Please try latest 5.4.5 debug build, it wont add the cipher automatically, just print a notice log now. /usr/local/lsws/admin/misc/lsup.sh -d -f -v 5.4.5 This change will be in 5.4.5 build 3 as well.

Thank you for the feedback. We certainly want to compare the performance using the best available cache system for each web server. Nginx FCGI cache is a server based cache, similar to litespeed cache, which is server based cache, people always believe Nginx FCGI cache is the fastest cache for...

You can tell us here if it is not confidential, or write an email to support @ litespeedtech . com .

done.

We can update our default template to include the

You can update to 5.4.4 build 8, or upcoming 5.4.5 build 0. /usr/local/lsws/admin/misc/lsup.sh -f -v 5.4.5 You can also use "strace -tt -T -p <pid_of_99%_cpu_process>" to check what it is doing.

Google Analytics use Java-Script on the client side, server side cache wont affect, same for Adsense.

Thanks for the confirmation.

We have pushed 5.4.4 build 3. please try the new version. If it happen again, please generate some debug log for analysis.

We will certainly add that to our feature requests. Implement that will take time. If staying with the current layer4 Anti-DDoS service is the only choice, you cannot use LiteSpeed now. Sorry about that.

Can try LIteSpeed built-in anti-ddos features. https://www.litespeedtech.com/solutions/anti-ddos https://www.litespeedtech.com/solutions/anti-ddos/recaptcha https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:mitigating-ddos-attacks could be better.

That's true that RemoteIPProxyProtocol is not supported by litespeed. so the extra header sent by the layer4 proxy breaks the SSL handshake.

checkout a copy of the project of master branch, then backup and replace your current lscache installation with those files.

can try pkill -USR2 litespeed instead.

Unfortunately, you did not enable debug logging at all. You should practice that when error is not happening, so you can do it properly.

for native LSWS setup, the log file is under /usr/local/lsws/logs/

It wont affect standard edition. you need to stay with standard edition.

correct.