LiteSpeed Cache - Community 1.0.4.3

[Alpha1]

Is there anything we need to change coming from vbulletin? When we installed it we followed these instructions for vbulletin.

 

[lsKevin]

Changes since vbulletin:

1. We no longer recommend putting cache root in /tmp, as it may get filled up. Instead, try /home/lscache or something else.
2. If you have any left over rewrite rules from vbulletin related to the cache in the .htaccess, those need to be removed.

The last step is to add the xf plugin and modify the .htaccess accordingly, but I'm thinking you already did that?

 

[Alpha1]

The last step is to add the xf plugin and modify the .htaccess accordingly, but I'm thinking you already did that?

Yes, I did. Thanks for the support @lsKevin !
All seems to work well now.

 

[lsKevin]

Perfect, let us know if something doesn't work quite right, we'll look into it!

 

[Alpha1]

I appreciate it!

 

[Alpha1]

Are any special settings needed for Vaultwiki?

 

[lsKevin]

I think the simplest way to find out would be to first cache a wiki entry, then edit it and see if the edit is applied. Note that the caching and the checking should both be done on a logged out/private browser, and the editing in a logged in browser.

I have a feeling that the editing doesn't go through any of the normal XF hooks (and thus will need customization), but they may.

 

[Alpha1]

I am getting hundreds/thousands of Redis read errors per day:

Error Info
CredisException: read error on connection - library/Redis/lib/Credis/Client.php:1104
Generated By: Unknown Account, Today at 12:02 PM
Stack Trace
#0 /library/SV/RedisCache/RedisDataRegistry.php(198): Credis_Client->__call('exec', Array)
#1 /library/XenForo/Dependencies/Abstract.php(147): XenForo_Model_DataRegistry->getMulti(Array)
#2 /library/XenForo/CssOutput.php(594): XenForo_Dependencies_Abstract->preLoadData()
#3 /css.php(12): XenForo_CssOutput::run()
#4 {main}
Request State
array(3) {
  ["url"] => string(264) "https://forum.com/css.php?css=bb_code,cta_featuredthreads,df_footer,faqe_font_awesome_rating,login_bar,message,message_user_info,nflj_ams_tab_links,nflj_ubs_tab_links,thread_view,toggleme_auto,toggleme_manual,xengallery_tab_links&style=2&dir=LTR&d=1487330185"
  ["_GET"] => array(4) {
    ["css"] => string(199) "bb_code,cta_featuredthreads,df_footer,faqe_font_awesome_rating,login_bar,message,message_user_info,nflj_ams_tab_links,nflj_ubs_tab_links,thread_view,toggleme_auto,toggleme_manual,xengallery_tab_links"
    ["style"] => string(1) "2"
    ["dir"] => string(3) "LTR"
    ["d"] => string(10) "1487330185"
  }
  ["_POST"] => array(0) {
  }
}

Turning of LiteSpeed and using Apache resolves this. It also speeds up the site when I use Apache + Redis.

 

[lsKevin]

How are you using Redis cache? Is it used to cache the full page?

 

[Alpha1]

I use these addons:
https://xenforo.com/community/resources/redis-view-counters.4366/
https://xenforo.com/community/resources/zend-redis-cache.3965/

 

[lsKevin]

A couple questions about your environment:

1. What OS are you using?
2. Which php 7.1 are you using? Regular php or lsphp?

 

[Alpha1]

Debian 7.
lsphp7 PHP Version 7.1.1

 

[lsKevin]

So we think it has something to do with how PHP was set up.

A few questions:

1. Are you using any control panel? How are you configuring LSWS to use its PHP? (e.g. lsws config, plesk config, etc.)
2. How did you install the LSPHP binary? Through debian package manager, compiled using our web admin, etc.
3. When you check PHPInfo on both Apache and LiteSpeed, are they both using the same ini?

 

[Alpha1]

1. We are using DirectAdmin as Control Panel
2. We compiled the PHP-binary from the Litespeed webadmin-panel
3. The PHP-versions for Litespeed/Apache are different. The PHP-version for Apache is compiled in DirectAdmin. They are also using different php.ini files

 

[lsKevin]

When you compiled PHP through the web admin, did you enable redis support? If so, do you remember what steps you took?

Another thing to check is to compare the php.inis. If phpinfo doesn't mention anything about redis, it might not be loaded in PHP, which would explain why it's not working with LiteSpeed only.

 

[Michael A.]

Michael A. updated LiteSpeed Cache - Community with a new update entry:

LiteSpeed Cache Community - 1.0.4.3

• [Bug Fix] Added back missing features caused by git conflict.
  
• [Clarification] Clarified some tooltips regarding .htaccess rules.

Read the rest of this update entry...

 

[The Dark Wizard]

How are the performance gains compared to something like Memcache?

Any one got any stats?

 

[lsKevin]

Hi @The Dark Wizard

Memcache doesn't do full page caching, as far as I am aware. Memcache will do caching within PHP/in the backend. LiteSpeed Cache is a full page cache. When a cacheable page is visited, we create a static version of it. The next time someone visits the same page, they will be served the static version, so PHP is never loaded.

Note that as of this moment, only logged out users can be cached with our cache. Since logged in users have some private information in what they see (e.g. a Hi The Dark Wizard!), they cannot be served from cache accurately.

The difference between our cache and most other cache plugins is a smart invalidate system. When someone posts a reply to a thread or creates a new thread, relevant pages will be invalidated, while non-related pages will still be in the cache.

This might be a lot to take in, but hopefully it helps. Let me know if you have any questions about this!

Cheers,
Kevin

 

[The Dark Wizard]

Hi @The Dark Wizard

Memcache doesn't do full page caching, as far as I am aware. Memcache will do caching within PHP/in the backend. LiteSpeed Cache is a full page cache. When a cacheable page is visited, we create a static version of it. The next time someone visits the same page, they will be served the static version, so PHP is never loaded.

Note that as of this moment, only logged out users can be cached with our cache. Since logged in users have some private information in what they see (e.g. a Hi The Dark Wizard!), they cannot be served from cache accurately.

The difference between our cache and most other cache plugins is a smart invalidate system. When someone posts a reply to a thread or creates a new thread, relevant pages will be invalidated, while non-related pages will still be in the cache.

This might be a lot to take in, but hopefully it helps. Let me know if you have any questions about this!

Cheers,
Kevin

It does!

I noticed in the FAQ a pro verison is coming for logged in users.

Any ETA on that ?

Been using Litespeed for a few years now and I would love soemthing like this C:.

 

[lsKevin]

No ETA on the pro version. We are close to releasing a test version for WordPress. If that goes through without issues, XenForo is likely next in line for that logic.