its working and it really change the speed of my site
great mod
installed
MOTM

star - I've never encountered that error when using Memcached on vBulletin, do both your websites have unique prefix's assigned in both the config.php and vB Optimise settings (assuming you're using it on both websites)?.

I'd try running one site with Memcache configured and seeing if the problem occurs, if not trying both sites and then seeing - but with unique prefix's there should not be any collision.

Deceptor, thanks for the reply. I have not set up the second forum to use memcache as per my original mistake - I had setup memcache on the server but completely failed to activate it in the vB configs. All I have done is actiavte it (with and without a prefix) on one of the forums.

I am going to try it on the other forum to see if the same error occurs when editing posts.

In the mean time I believe I can report substantial performance improvement on the site with filecache running with your product in combination with the yslow mod.

I do hope that I can get memcache working as it is bound to be even faster and may allow me to investigate the even further potential of using your commercial version.
(sorry I had failed to mark as installed - done that now - I had had it tagged but was not holding off marking as installed - this is an excellent mod and beautifully executed)

star - Thanks for the information, given this is surrounding the datastore you can opt of using it within vBulletin (in the config.php line, comment out: $config['Datastore']['class'] = 'vB_Datastore_Memcached';). If the bug doesn't appear then, it's the vBulletin Datastore.

Alternatively, you can disable Datastore Cacher on vB Optimise - however this only forces custom datastore items to use the correct datastore method (as vb doesn't handle them correctly).

Let me know if I can be of any further help, Memcache will surpass Filecache immensly (Memcache uses RAM, Filecache uses your HDD) so it'd be great if you got it working without problems :)

Thanks Deceptor !

So, please help me ensure that I have this correct...

If I comment out the line

from the vB config.php
BUT leave the other memcached lines in the file as is then memcache will not be used by vB's natively coded datastore - which you state is sub-optimal -
BUT AT THE SAME TIME switch vBOptimise's cache setting to memcache then we will still get memcache performance enhancements for all "customised datastore" and therefore won't be as good as having the vB native datastore using memcache PLUS the customised datastore through vbOptimised...

Not sure I got that down properly, will do some testing and see if I can get my head around it. I think that what you are suggesting will just bring up the original issue that prompted you to ask if I had the memcache setup properly in vB config.php to begin with...

Will

I appreciate the support very much!



[UPDATE]
Yes, as I currently have the memcache off in vB's config.php to prevent the wierd error; I have reenabled memcache as the optimisation method in your product and get the same/following results when I run the system test:
In this state I can confirm that I can edit and save posts without the "maxloggedin" error showing.

I take it that this means that the product is going to have NO effect and that I need to get the vB side sorted before I can proceed.

In which case falling back to filecache is my next best option>?

OK here's the thing.
I have configured my other less-modified board to use memcached by uninhibiting the memcached datastore section of the config.php. Interestingly the board crashed out complaining that it couldn't find the vboptimise scripts - which was unexpected as it is not a mod I have added to that board but I figured that it must have something to do with data in the cache so I set the prefix option and the board operates as normal - furthermore it does not have the 'maxloggedin' error. What this tells me is that one of my hacks is causing that on my bigger board and I would seriously like to find out which ... Any tips on where to start with this - unsure that I can easily start switching things off systematically without bothering my users but will do that if necessary - is there anything I can do that will help me troubleshoot the error if I can get it to start happening again.

Thanks for the help so far and I understand that you don't support the base code itself and nor will vb.com so I am just asking for any tips - completely understand if you want me to take it to another thread.

Will

[UPDATE] This mod works PERFECTLY on my other board - all I had to do was ensure I used the prefix for the datastore in config.ini and went through the other optimisation settings recommended by Deceptor's product - awesome - thank you this is a fantastic product!

When I get my other board sorted I will be purchasing this for both sites.
Will

OK (sorry to be avalanching in this product thread Deceptor and others :oops: ) but I need to clarify something further:

I have the vBOptimise product on and passing all tests on my smaller board - it does not throw the wierd 'maxloggedin' error on editing and saving posts. This is therefore a "full" implementation of this product and the vB core memcached datastore engine...

Further I have commented out the "$config['Datastore']['class'] = 'vB_Datastore_Memcached';" line - and only that line in the bigger board config.php and can say that the vBOptimise system tests are all passing - so this is encouraging - especially as I can still edit and save posts there ...

BUT and this is a big BUT... Despite having separate "prefixes" for the two sites they seem to be merging a lot of the common (but different) cached data - ie my forum logo, all the ads served up by openx - various image elements from the css's.

I have had to switch to filecache on the smaller board to stop it inherriting all the stuff from the bigger one.

I doubt that I have the expertise to sort this out right now and it is very hard to full explain - I also don't want to spam the thread of your excellent product.

So I will await any suggestions otherwise I'll sit tight and see what my users say - if its somewhat better I'll leave it at that for now!


Thanks again and sorry for the verbose troubleshooting posts!

Will

Hi star,

Don't worry about the mass of posts, just glad you can provide me all this information to help you diagnose the issue :)

Firstly, regarding the "cache collisions", I understand you've set alternative prefix's within vbulletins config.php - however that prefix is only used by vBulletin. vB Optimise has its own prefix within the main settings (default is "vbo_"), make sure those 2 are seperate on your forums and the cache collision should go away.

Secondly, regarding the mod invoking the "maxloggedin" issue. I'm afraid it could be any, mainly those that interface with the datastore itself (most probably). You could try backtrace the error the root of the cause but that'd be tricky - the simplest method would be as you said, trial and error until the error goes away.

If there's anything I missed out let me know, those 2 seem to be your main current issues :)

Deceptor:
"Optimise has its own prefix"
:Doh: yet again I am so far ahead of myself I have missed the obvious - of course it does! This will make a real difference. Thank you for the attention to detail. Your product is really well thought out and implemented.
I will dig into the 'maxloggedin' issue and right now I will make sure that the vbo cache prefix is properly set.

Thanks for all the help
Will

No problem star :) Let me know if you have any further questions or issues, enjoy!