I have a stripped down version ready for vb 3 but haven't decided if I want to post it yet as I am running vb 4 so vb 3 support would be spotty for me.

I understand caching, but I had problems, counter didn't changed even after ttl and max ttl and gc interval expired. Cache items should be forced to renew, but it didn't worked for me. Maybe I need to test it further? Will see, and I report here if I manage to have it working with xcache.

EDIT:

Still not working.

If someone knows better how to setup xcache, here's my xcache ini:

With these settings for xcache.ini and with this setting in config.php for vbulletin:

my page hit counter doesn't work. When I disable datastore caching counter starts to count. What is the problem, I don't know. If anyone has an idea, please, tell me.

EDIT2: Just checked, after I disable datastore caching, counter is updated with new page hits. So counter does work, but I'm unable to set automatic flushing of counter to make changes visible. For some reason change in counter isn't propagated while caching is on. Any idea how to set it right?

You STILL don't get it. It WORKS! I had it working with xcache just fine. It WILL NOT update the counter on the forumhome until the cache refreshes itself. But the counter is still being updated in the datastore. That is how caching works. I don't know how else to explain it to you so you will understand.

Yes, it works, as I said in edit2, but thing is, I don't see it. As long as the xcache is used, I don't see it. That's the problem. I want to see it, that is whole point. How to make cache to refresh itself automatically?

Other things work as far as I can tell, but your counter doesn't, not automatically, not for me.

I agree that there can be something that I set up wrong, but I can't tell what.

Arrggghhhhh! It works, it just doesn't change the number until the cache refreshes. When it refreshes, you should see a jump in the numbers as they are being added to the datastore even while the cache is on. You will notice that the threads and posts numbers don't update either until the cache refreshes. That is how caching works. There is no way to refresh the cache other than the settings and if you want it to refresh on very page load, then caching makes no sense for you to use.

Ok, I understand what you are saying and I'll turn caching and wait.

When I installed and waited for about a day, nothing changed. Now I wasn't waited that long, but I will.

Finally! ;)

Caching gives you the added benefit of speed as it reads from the cache and doesn't do the queries on every page refresh. But there is a trade-off, like with counters. If you have a lot of users on the site at one time, caching is the way to go to keep resources manageable.

You can always look in the db at the datastore and see the counter has increased so you know it works. You just won't see the higher number until the cache refreshes is all. It looks like your caching interval is set to an hour, unless I'm reading it wrong.

Do you have idea where can I see my caching interval? And how to change it?

Ok, I see now that it works. :) I'm very much ashamed. :( You're right, I just needed to wait. I think that my problem was caused with using datastore prefix and certainly I was very impatient afterward.

Thanks for your patience. :)

It gets confusing sometimes, I know. I have been there myself a few times. No harm done. ;)