Caching in vb5. Broken??

[philg]

I know you want the site to be fast even if the code isn't but the caching method you use is requiring visitors to contantly refresh the page to get the latest version.

Just disable it or explain your reasons for having it.

[Wayne Luke]

You shouldn't have to refresh every page. Though there are some occasional things that require refreshing. I think I refreshed my page twice there today. Some things like Activity streams are cached for 5 minutes just for performance purposes.

[philg]

Most topic pages that I viewed today haven't updated from the last time i saw them which was a few days ago. I know that there are new posts because the forum view, oops directory view shows the number of replies which is greater than what's showing. I have to refresh the topic page to see the new replies.

I'm using Chrome browser.

[digitalpoint]

I think he's referring to the server caching that's being done outside of the application.

It looks like the entire site is using Varnish now (which is probably why it's a lot faster now). https://www.varnish-cache.org/

Unfortunately, it's being a little too agressive with the caching imo... like it shows me as being logged in from before the whole thing was reset days ago. Then a hard refresh (which is slow) refreshes it properly for awhile. Then if I go back, I'm back to being logged in to a non-existent user account.

[beishe8]

Unfortunately, it's being a little too agressive with the caching imo... like it shows me as being logged in from before the whole thing was reset days ago.

Well,on my test site my test user is logged in for two days.
Can't get rid of him/her.(Clearing my browser has no effect)

[Lizard King]

Varnish require several custom configuration options to run correctly. Unfortunately none seems to be applied for demo.

[Guest]

That's a fast way to speed up a web page without actually fixing any SQL or code, Varnish!

[dilbert]

It looks like the entire site is using Varnish now...

I hope this is something people using shared hosting can install.

[Wayne Luke]

I hope this is something people using shared hosting can install.

Doubtful... However performance enhancements are being done on the software. As well as query reduction so by gold, Varnish shouldn't be needed by small sites on Shared Hosting.

[AlexanderT]

It makes me worry if you'd need to use Varnish or another external caching solution to improve the loading times of a demo site with the little traffic it receives. Not the kind of performance fix some might have been hoping for.

[Wayne Luke]

It makes me worry if you'd need to use Varnish or another external caching solution to improve the loading times of a demo site with the little traffic it receives. Not the kind of performance fix some might have been hoping for.

vBulletin.com is a large site with a lot of traffic and processes outside the Demo. It isn't on its own server. It is sharing servers with everything else including the member's Area, sales systems, support systems, these forums. Varnish is used on the entire system, not just the demo.

[Guest]

So Varnish was just configured wrong on the demo site?

[Wayne Luke]

I would say its configuration is over zealous. I have no control over that. It isn't really hiding the performance issues either. At least not in my opinion. We should have new builds coming soon that actually fix the problems.

[dilbert]

... small sites on Shared Hosting.

You've mentioned "small" sites a few times in other posts. It feels like the little guys are being left out in the planning for vB5.

[Wayne Luke]

You've mentioned "small" sites a few times in other posts. It feels like the little guys are being left out in the planning for vB5.

I don't see that. Small sites will gain from performance enhancements and bug fixing just the same as large sites. However a larger site will have other things at their disposal for performance such as multiple VMS or Dedicated Servers, Varnish, Sphinx, and more.

Shared Hosting is and always has been limited on what kind of optimizations we can apply outside the code itself though. People don't run large websites on shared hosting.