Most excellent work. Best Hack I have seen in a long time.

Congratulations! really cool.. I agree with you CodeMonkey.

I'm not sure but i'm sure vbSEO uses lots of resources?

Tested a bit on my server, as promissed. Didn't found noticeable difference: server load (average) unchanged, page generation time (average) unchanged.

May be, I do somerthing wrong :)

Probably, effect can be gained in 2 cases:

- on apache+modphp, with bunch of active processes.
- if additionad mods are written dirty.

Config: (php 5.2.6/eaccelerator/nginx) + (vb3.7.4/vbseo/memcached) + (Core Quad 6600 / 4Gb Ram)

Top = 1.5 (100% = 4)
~200 000 php page hits dayly.

You must be doing something wrong , i have nearly the same setup as you and dual core server 4gb ram and ive noticed my forum is like 30% faster and all my members say its faster aswell :)

If i'm correct, you have incredible number of queries at first page and not optimized modifications. In this case vboptimize should help, surely.

Don't you find a reduction in the number of queries?

I found a lot better results using the xcache method then memcache so far.

mindhunter77 - If vB Optimise is reporting an issue with eAccelerator, chances are eAccelerator not working correctly. Might wanna check your setup, or ask your host for assistance.

Vitaly - I make no claim to instantly reduce server load, but it may impact it if vB Optimise has done a lot of optimisation ontop of what you had before, so a reduction of two queries wouldn't be significant enough - that said it depends on the amount of users you have active and your server. What cache method are you using?

KevinL - I'd agree, XCache does seem to be slightly better than memcache, mostly with page generation time :)

As for what I intend to do with vBSEO, the same as vBAdvanced really, optimise.

Same problem here. There is definitely a problem with detecting eacc, so eacc support is NOT enabled after all!

wolfstream - vB Optimise will check the function 'eaccelerator_get' is available, if not it will return false giving you that error, and people here have said eAccelerator is working fine, what version of eAccelerator do you have?

Just had my host remove eaccelerator and install xcache :)

Enabled xchache and got many lines reporting this:

Warning: xcache_isset() [function.xcache-isset]: xcache.var_size is either 0 or too small to enable var data caching in [path]/includes/class_activecache_methods.php on line 163

Now I cant get to anything. IS this because I bneed to enable it in config.php first?

Version 1.2.2 Modules Built cacher Readonly Protection N/A Opcode Cache enabled, 33,554,432 bytes, 1 split(s), with 8192 slots each Variable Cache disabled Shared Memory Schemes mmap

Hostboard - This is due to your XCache setup, edit your php.ini and change the xcache.var_size as this allocates the available space for XCache to store variables, check out the XCache website for more information: http://xcache.lighttpd.net

I personally have XCache var_size set to 128M, for 128 MB :)

Edit: Saw your edit, remove XCache from config.php, you may also need to disable plugins to get back into your forum ACP:
That goes in your config.php to disable plugins :)

From phpinfo:
This is the latest downloadable version (2008/05/18)

Wolfstream, I've attached a basic php file below that will test every function needed for eAccelerator in vB Optimise, it can be uploaded anywhere, just visit it by url and let me know your results :)

Thanks.

Thank you very much logicuk, I appreciate your donation and support towards this product :)

Bumped from 32 to 128 and all is now happy. Thank you :)

Glad everything is all working now Hostboard, let me know the results you're getting from vB Optimise, or if you have any further issues :)

No problem mate :)

Do you have a time frame on the next release? thanks logic

Let's see here

Eaccelerator works. I've tested this and found it to be so. It's really easy to test if it works

Eaccelerator was compiled using THEIR recommended setup

YOUR setup doesn't detect eaccelerator functions. That's a problem in your setup. This needs to work with the eacc recommended settings, not the other way around.

There is definitely a problem here, as represented by at least two people. The problem is with how eaccelerator is configured. You shouldn't HAVE to reconfigure a server application for one plugin, in fact most people can not.

The recommended values for eaccelerator configuration (which, btw has worked for years without fail):

Changes insisted by your code (and ONLY your code, btw):
Again, this should be done properly, so that individuals DON'T have to recompile and reconfigure eacc, especially when they can't.

While I appreciate the feedback wolfstream, I think you're forgetting one vital thing here. Without the extension installed it is impossible for any php script to use eAccelerator functions, vB Optimise works exactly like vBulletin does for its datastore system for eAccelerator, and just about every other PHP script I've found that uses eAccelerator.

Please do not make claim there is a problem with the script when it was instead a problem with your eAccelerator setup. Ofcourse eAccelerator will work without the functions available in PHP, as it also works as a php optimiser in whole :)

Even vbseo cache doesn't work with eaccelerator compiled without ' --with-eaccelerator-shared-memory \ ' , So there is no problem with vb optimse,

@wolfstream
Incorrectly setting up eAccelerator is your fault - don't blame this script for a crippled eAccelerator installation.

Here are a list of options that affect performance and you might want to add to the "Optimal Settings Check"
There are some smaller ones such us
Donated 10$ Not as much as lugicuk but 10$ you get :D

Great job the speed difference is astonishing ^^ the vba module is really a miracle ^^

Thanks :D

NolF - Thank you for your donation :) Regarding those options, most I've let out for now on purpose, regarding your first group of options, they come at expense of features, and it is my aim to be able to cache these, rather than drop them for performance, like I did with the forumhome WOL.

As for the other two, the forum drop down menu maybe something I cache too, and GZIP isn't always safe on all server setups, so I didn't put it in there because people would blame my script for telling them to use GZIP when it did damage it instead of good :)

But thank you for the suggestions, I'll probably concentrate on these areas in the next version :)

That's so incorrect it's not even funny. Eaccelerator works FINE without the above compiled option. If it didn't, it would be put in the recommended settings.

I've had eaccelerator running for years. Cache? Right now, it's running at 30.30% (155.12MB/ 512.00MB), with the top script (right now) being accessed over 4k times since the last time it was cleared. There is no way you can NOT tell me eacc does not work properly, because it does.

Again, wrong answer. If you don't know what you're talking about, please, don't try to step in and say you do. From their INSTALLATION GUIDE!

Eaccelerator was not installed incorrectly at all. This product requires advanced setups and should be modified to work with the EA recommended settings. I've been installing EA the exact same way (eventually you just script it ;)) for clients for years, numerous clients, over a good 30+ servers. Have ANY of them complained about it 'not working'? Nope.

Again, using the above settings, EA has worked, and has cached scripts for years. Right now, I'm at about 5GB cache (should probably clean some of that up ;)), but it most definitely DOES work properly, using the recommended , out of the box, settings.

This is not a problem with anything but products trying to force users into an advanced EA compile.

As I said above wolfstream, eAccelerator will work at caching scripts because that's the main purpose of eAccelerator. But for PHP scripts to actually use eAccelerator functions it requires the extension. I've also said this is how vBulletin does things, and other scripts, a member above also pointed out vBSEO.

So unless you know a magic way for my script, vBulletin, vBSEO and anything else out there to use eAccelerator functions without the extension installed, please tell me, I'm always open to suggestions. Otherwise please stop making claim that there is something wrong with my script when clearly there isn't.

Regarding the eAccelerator recommended install, they don't expect most server setups to have scripts which use eAccelerator, and for the purpose of just caching php, it'll work.

Hello i use the thanks mods the query in postbit or postbit legacy can be cached??
Sorry for this stupid question :)

http://bart.eaccelerator.net/doc/php...emory_php.html

It's clearly stated that you have to compile eAccelerator with support for shared memory if, well, you want to use shared memory!

To some extend it does: It caches PHP opcode.
But the content cache functions are non-working if not compiled like stated above.
Try to use eAccelerator as vBulletin datastore cache.

If you call enabling a fature (that was on by default in eAccelerator < 0.9.5) "advanced" yes, it is.

Just incase you decide to continue this pointless argument, I'll put your mind to rest:

http://www.eaccelerator.net/wiki/CompileConfiguration

Please take real care when reading "Include eaccelerator shared memory functions".

If you still have an issue, I recommend you take it up with eAccelerator themselves.

lolo - It doesn't cache all mods I'm afraid, the only mod this currently extends to is vBAdvanced.

@EAccelerator
So Glad I went with XCache :D

@Deceptor
As a consumer I wouldn't find it an issue to be commented (by the mod) what features may be crippling my forum, even if I leave them on because I want the feature it would work as a centralize reminder of what you can do to improve performance. Some of us may have our mind somewhere gone whilst setting up the forum and enable some of this features which we don't really want or need.

I don't know up to you, but as an additional box indicating the concerns you commented wouldn't really hurt anyone, and benefit many ^^

Regarding the forum jump, wouldn't it be an issue to cache? different people have access to different forums and hence would have different forum jumps... Personally I would love the option I have 279 forums in my forum jump :S

NolF - Determined by reasoning and personality I guess, not everyone would see it the same way. So I guess cache instead of suggestions will be better :)

As for the forum jump, I never said it'd be the easiest task :)

:o Love your dedication mate ^^

haha some misleading posts went MIA

Thanks once again :D

Bad attitude? I'm not the one with the 'bad attitude' here. I'm the one being attacked by numerous individuals, simply because I made a truthful statement.

RTFM. The installation guide tells you EXACTLY how to do things here. EACC works beautifully with, or without the line added, both in optimization and CACHING. If it didn't, I wouldn't be sitting with close to 5g of cached data, and files with over 4k pageviews, WITHOUT adding it.

If eacc DIDN'T work as they suggested, I would have known about this years ago, when installing things for clients.

Just because vb wants things done a certain way (and yeah, that includes the SEO garbage) doesn't mean it's the way to do things. The manufacturer of the product (in this case eaccelerator) will always tell you how to install the product. In this case, they gave very basic instructions, and those instructions work.

As far as the 'bad attitude' comment, that's not even the case here. When developers take actions like this, and force NON STANDARD configurations on individuals, then blame it on the 'system', or wtfever, that rides solely on the developer. It's not the USER'S fault the developer can't make the product work when compiled as recommended. It's not the USER'S fault the developer wants to force people to recompile with their own special settings, that's the developer's fault.

And on that note, I will, in fact, uninstall, and unsubscribe. No need to keep beating a dead horse when people don't want to listen to the truth, and the developer has no intentions on making the product work with the RECOMMENDED SETTINGS.

I installed this mod in the middle of the day on the 20th. Here is some hard proof that it is working wonderfully; stats from my database server's bandwidth. (outbound is mostly database data going to the web server to render a page)

https://vborg.vbsupport.ru/external/2009/02/103.jpg

pay no attention to the data compiled for today the 22nd as it is not complete

I should include that last sunday's traffic (14th) was very similar to this sunday's (21st). I am using memcache. There is also a similar trend on the web server's inbound data.

Outbound bandwidth has decreased by ~47% on the database server!!! (based one day of similar data) What does this mean for most of you? Fewer database queries = lower server load = faster site = happy forum users!

Bottom line: This mod is going to save me money as I am currently going over on my bandwidth as well as improve user experience!

Nominated for mod of the month and will be donating

wolfstream - I really think you're not getting the picture here.

Default eAccelerator Install = Cache PHP Scripts

Shared Memory Extension = Ability to use functions to cache custom data through eAccelerator.

My script, and every other script out there (not just vB) needs shared memory to be able to use eaccelerator_get, and other functions. Even the links myself and Andreas provided stating this on the eAccelerator website tell you the same.

I really cannot see anything else I can say or do to show you that it is impossible for vB Optimise to use shared memory without the shared memory extension installed.

tpearl5 - I'm glad it's had such a great impact on your forum, and thank you for your donation :)