Separate names with a comma.
Discussion in 'LiteSpeed Cache' started by kan3, Feb 1, 2011.
Is LiteSpeed Cache compatible with IP.Board 3.1.4?
Litepspeed Cache uses rewrite rule to fine tune the cache policy, only cache pages that is safe to be cached. It can apply to IP.Board.
I've seen cache configuration help offered for vB and vBSEO. Any chance we can get something for IP.Board?
I can give you FTP access to my site if it would help.
pls pm the access.
PM sent... thank you!
Did you get any help? Are you still using the litespeed cache? How is the performance?
Yes, webizen has been very helpful, and will publish the config in the wiki once finalized...
Cool, glad to hear that. But how is it going? Do you see a better performance? Is this caching technique better than xcache?
It's completly different. Apples vs oranges.
Oh, had no idea about that. So what does this cache do? I mean any benefits?
It caches whole website, so that next guest downloads cached one wich is actually static page (no php usage at all).
wow, that would be fast. Are you using this cache with IPB?
Yes, PM with URL
We've used many caches over the years. We've specialized in high performance IP.Board applications.
The first is separate cache/image/js/uploads subdomain which you may run with LiteSpeed Cache or Varnish on separate system or same.
You can also cache the main domain however this *can* have negative effects. We mostly noticed none, however we havn't tested LiteSpeed cache in particular.
FYI, the final result is subject to change, but the current solution being tested works on the entire main IP.Board domain. Guests and logged in users.
Yes this works aslong as whatever http accelerator doesn't cache changed data.
The best method for this is uncaching cookie'd requests. (Logged in users) unless the backend can check periodically every few seconds for changes (smartly, less per other things or uncaching commony requested URIs) shoutbox and such will uncontrollably cache and show stale data.
When you cache using the options IP.Board has separately and enable main domain caches for agents with no logged in cookies for boards with public data commonly requested.
This is the best method and for most boards causes very low requests. Guest requests can be uncontrollable, most logged in users don't do insane req/sec so its mostly cached.
We did Varnish over LiteSpeed on a WHM/cPanel live production system with a few dozen clients and it almost dropped the load to sub 1 and no complaints for days. We switched back with no complains, when notifying clients they did notice a large performance increase.
for us Varnish instantly will saturate the connection between client and server vs litespeed/apache/lighttpd only saturating bit by bit till it's done.
Hey Chris it's good to see you bro.
whos this lol