Quote:
Originally Posted by Deceptor
tmc - While I agree it could be holidays, the templates query is the largest query vB executes, so I would expect some impact. In anycase, it'd be nice to see the results over a longer period 
|
Well, I'm sure most showthread queries surpass the template queries in size.. Although I agree it's a most ridiculous way to use the "V" in "MVC" so I hope that changes in 4.0. I'm hoping for something like CodeIgniter where we get a Views folder with all the template files. (And of course the means in default vBulletin to cache these.)
I can't think of a better word.... but would it be better for "latency" if we were to only use the Xcache VAR cache for this modification, and tell vBulletin to use nothing but Memcached? (Meaning: So not everything is trying to use the same cache at once)
I was a little foggy on that anyway, because I'm aware that Memcached is capable of a lot more than just caching vB's Datastore, but it seems that if you don't configure vBulletin to use Memcached for the Datastore, then Memcached won't bother caching any other objects into memory, such as query results, etc.
So I guess we can't pick and choose, huh?
I guess I'd be fine with that anyway... This mod = Xcache's var cache, vBulletin = Memcached