SEO

I have two forums on a single server, each with their own copy of vbSEO. I've recently installed xcache, but haven't configured it (will do so shortly) or turned it on in vB's config.php for either forum.

Really I just want to be clear, should I be turning it on there (on the vB config.php side) AND in vbseocp for each forum? Just in vB with the prefixes? Or just in vbseo? None of it is very clear.

Hello,

vBSEO has its own Caching implementation that works/is configured independently from vBulletin. If you have more than one vBSEO forum running on the same server, you should define custom XCache variable name in config_vbseo.php:

__________________
Oleg Ignatiuk / Crawlability Inc.
Support Team Launches New DeskPro Powered Tool Enhanced Support at Your Service

vBSEO 3.2.0 Launched - Maximum Overdrive for Your Web Traffic! Over 100 Instant SEO Optimizations

6X Traffic - $1400 in One Day with vBSEO! Imagine What the vBSEO Patent Pending Technology Can Do For You.

Hi, Oleg.

Thanks for the quick response.

Just to be clear, I should enable XCache on the vBSEO side, and *not* in the vBulletin config.php?

And I should change 'vbseo_storage' to something unique for each site? Such as 'site1_storage' and 'site2_storage'?

You can have it enabled both for vBSEO and vBulletin or only for one of the cases, it should still work.

Yes, exactly.

__________________
Oleg Ignatiuk / Crawlability Inc.
Support Team Launches New DeskPro Powered Tool Enhanced Support at Your Service

vBSEO 3.2.0 Launched - Maximum Overdrive for Your Web Traffic! Over 100 Instant SEO Optimizations

6X Traffic - $1400 in One Day with vBSEO! Imagine What the vBSEO Patent Pending Technology Can Do For You.

So there's no benefit to enabling it on vB if I'm doing so on vBSEO then? If so, that makes my life easier, and I don't have to ask if all four instances (config.php x2, and vbseo_config.php x2) each have to have unique variable names.

Thanks so much for the information!

Yes, I've been thinking the same. I'd like to know, too!

Thank you!

If you enable it in config.php that will enable caching for vBulletin itself, so it might make sense to enable both of them.

__________________
Oleg Ignatiuk / Crawlability Inc.
Support Team Launches New DeskPro Powered Tool Enhanced Support at Your Service

vBSEO 3.2.0 Launched - Maximum Overdrive for Your Web Traffic! Over 100 Instant SEO Optimizations

6X Traffic - $1400 in One Day with vBSEO! Imagine What the vBSEO Patent Pending Technology Can Do For You.

Okay, I need to circle around to the previous question then.

Do I need to set 4 different unique variables then? One each for: Forum1_VB, Forum1_VBSEO, Forum2_VB, and Forum2_VBSEO?

Or should both VB and VBSEO for each forum share the same unique variable?

Sorry, Oleg. I just want to make sure I do this right and not corrupt the cache or cause server problems for myself.

You will need 4 different variables in this case.

__________________
Oleg Ignatiuk / Crawlability Inc.
Support Team Launches New DeskPro Powered Tool Enhanced Support at Your Service

vBSEO 3.2.0 Launched - Maximum Overdrive for Your Web Traffic! Over 100 Instant SEO Optimizations

6X Traffic - $1400 in One Day with vBSEO! Imagine What the vBSEO Patent Pending Technology Can Do For You.

Perfect, thanks for your patience.

Now I just need to figure out what settings to use for XCache, lol. But that's research for another forum.

I can tell you that you don't need much memory for the variable space cache (xcache.var_size) which handles the vB datastore and vBSEO cache. I've got several forums on my VPS and I've had to bump xcache.size (for the PHP caching) to 160M, but I'm getting by with just 4M for xcache.var_size and even that looks to be excessive.

Thanks, appreciate the insight. I'm just sort of cobbling together settings from different threads here, on vb.com, and another site.

Is the goal to keep the values as low as possible, but high enough to not get errors? Meaning, is there a downside to overdoing it?

If you allot too much memory, it just means there is less memory available to the server for other processing chores. The goal is as you stated - enough, but not more.