Helpful Information
 
 
Category: Management Articles
Speed Up Your Forums! vBulletin 4!

Hopefully this article will help your slow vBulletin 4 forum speed up a bit. :)

1. First of all, here are some admincp settings you can set, credit to eva2000 (http://www.vbulletin.com/forum/member.php?245-eva2000)
For vB 4.x try to DISABLE = set to NO these options

Admin CP -> vBulletin Options -> General Settings -> Use Quick Navigation Menu

Admin CP -> vBulletin Options -> General Settings -> Thread/Forum Read Marking Type - Database automatic forum marking is very processor intensive compared to Inactivity/Cookie based or Database no automatic forum marking, so if your mysql process is constantly pegged at 100+ % cpu usage, you don't want to be using automatic forum marking Database type.

Admin CP -> vBulletin Options -> Forums Home Page Options -> Display Logged in Users?

Admin CP -> vBulletin Options -> Forum Home Page Options -> Display Today's Birthdays?

Admin CP -> vBulletin Options -> Forum Home Page Options -> Display Calendar Events?

Admin CP -> vBulletin Options -> Forum Display Options (forumdisplay) -> Show Users Browsing Forums

Admin CP -> vBulletin Options -> Thread Display Options -> Show Users Browsing Thread

Admin CP -> vBulletin Options -> Thread Display Options -> Check Thread Rating

Admin CP -> vBulletin Options -> Thread Display Options -> Check Thread Subscription (disable to check if it's load related if not re-enable it)

Admin CP -> vBulletin Options -> Thread Display Options -> Full Next / Prev Links

Admin CP -> vBulletin Options -> Message Searching Options -> Automatic Similar Thread search

Try to ENABLE = set to YES these options

AdminCP -> vBulletin Options > Cookies and HTTP Header options -. Enable GZip HTML Output - Set to 1 for optimum results.

Admin CP -> vBulletin Options -> Message Searching Options -> Queue Search Updates

Admin CP -> vBulletin Options -> Message Searching Options -> Search Result Sharing

2. Store CSS As files - more info here (http://www.vbulletin.com/docs/html/stylemanager_css_as_file)

A complex CSS stylesheet can occupy quite a block of text when printed out in full. This entire block of CSS code must be included with every page viewed by your visitors, and with a lot of visitors over a long period of time this can mount up.

One of the beauties of CSS is that the stylesheet can be held in a separate file from the HTML content, allowing web browsers to store the CSS in their cache, negating the need to reload the stylesheet with every page viewed.

vBulletin allows you to have your stylesheets automatically saved to files by the system, resulting in lower bandwidth usage and faster-loading pages for your visitors.

To enable vBulletin to save your stylesheets as files, you must first ensure that your web server has permission to write and delete files within the clientscript/vbulletin_css directory.

You should then go to vBulletin Options > Style & Language Settings and switch the Store CSS Stylesheets as Files? setting to Yes.
https://www.vbulletin.org/forum/external/2010/02/8.png
After pressing the [Save], your stylesheets will be converted to files and saved into the clientscript/vbulletin_css directory.

Whenever you make a change to your styles that alters the CSS, the stored files will automatically be updated.

3. Enabling Datastore (http://www.vbulletin.com/docs/html/datastore)

To improve performance, vBulletin caches certain information which isn't updated often in the datastore, so that it doesn't have to be rebuilt every time it's needed.

Examples for this are

* forumcache - A serialized array with all the forums along with their options and permissions
* options - A serialized array with all the information set in the vBulletin Options
* profilefield - A serialized array of all the profile fields and their options.

The datastore data is stored in the datastore database table by default, but certain settings in the config.php file allow this to be saved in other places, to improve performance:
// ****** DATASTORE CACHE CONFIGURATION *****
// Here you can configure different methods for caching datastore items.
// vB_Datastore_Filecache - for using a cache file
// $config['Datastore']['class'] = 'vB_Datastore_Filecache';
// vB_Datastore_Memcached - for using a Memcache server
// It is also necessary to specify the hostname or IP address and the port the server is listening on
// $config['Datastore']['class'] = 'vB_Datastore_Memcached';
// $config['Misc']['memcacheserver'] = '127.0.0.1';
// $config['Misc']['memcacheport'] = '11211';

vB_Datastore_Filecache
This option saves the datastore data in the /includes/datastore/datastore_cache.php file. Reading from the filesystem is generally less load-intensive than querying the database.

To use this option, you'll need to make sure that the /includes/datastore/datastore_cache.php file is writable and readable by PHP. Usually this is chmod 777. Then, uncomment the following line in the config.php file.

(If your on a VPS or Dedi install XCache (http://xcache.lighttpd.net/) its faster than others. How to (http://www.vbulletin.com/forum/showthread.php?t=213267) - Install Guide (http://xcache.lighttpd.net/wiki/InstallFromSource)

4. Get rid of those rounded corners! Credit to Andy (http://www.vbulletin.org/forum/member.php?u=42356), original post here (http://www.vbulletin.org/forum/showpost.php?p=1991857&postcount=9).
One reason vB4 is slower than vb3 is the use of shading and rounded corners. Add this to the bottom of the additional.css template and your forum will speed up considerably.

* { -moz-box-shadow: none !important; }
* { -webkit-box-shadow: none !important; }

* { -moz-border-radius: 0px !important; }
* { -webkit-border-radius: 0px !important; }
Feedback from users, saying their forum loads faster.

5. Install vB4 Supercharged download it here (http://www.vbulletin.org/forum/showthread.php?t=229608). It does NOT work on 4.0.2 PL1 just yet, we have to wait until the author has updated the modification.

6. vBulletin 4 optimize htaccess (http://davidmchenry.info/2009/12/18/vbulletin-4-optimized-htaccess/) - add those contents to your htaccess.

7. Add to top of headinclude <META http-equiv=Page-Exit content=BlendTrans(Duration=0)>
<META http-equiv=Page-Enter content=BlendTrans(Duration=0)>

8. Download YSLow (http://www.vbulletin.org/forum/showthread.php?t=178286) - add the contents to your htaccess.

9. You can Improve Page Loading Time (http://www.vbulletin.org/forum/showthread.php?t=234486)

10. Enable Remote YUI: YUI (Yahoo! User Interface Library) script files are hosted locally on your server, you may however have them served from Yahoo or Google servers, saving you some bandwidth and potentially decreasing load times.
AdminCP > Settings > Server Settings And Optimization Options > Remote YUI to YES - Prefer Google.

11. In addition to this, check out articles from one of the worlds largest webmaser forums.

Optimize vBulletin 4 (http://articles.digitalpoint.com/content.php?r=7-Optimize-vBulletin-4)

If you are using Memcached servers:

Monitor memcached servers with vBulletin (http://articles.digitalpoint.com/content.php?r=14-Monitor-Memcached-Servers-With-vBulletin)

Thats it! If your forums have sped up a bit please let me know, if they have not and your using a VPS or Dedicated server, request for a server optimization.

http://www.vbulletin.org/forum/showthread.php?t=241782
http://www.vbulletin.org/forum/showthread.php?t=241783
More optimization

I said it once and I'll say it again, rounded corners don't and can not have an effect on how fast vBulletin generates a page. It's simply impossible that CSS could slow down the speed at which vBulletin retrieves data and sends it to the browser, CSS is a client side thing. What you are looking at is the speed at which your browser renders the page.

I refuse to believe this helps any until I see legitimate benchmarks.

I said it once and I'll say it again, rounded corners don't and can not have an effect on how fast vBulletin generates a page. It's simply impossible that CSS could slow down the speed at which vBulletin retrieves data and sends it to the browser, CSS is a client side thing. What you are looking at is the speed at which your browser renders the page.

I refuse to believe this helps any until I see legitimate benchmarks.

Exactly...it depends on the browser. As Chrome and Safari usually faster (both in javascript and CSS rendering) than Firefox it can have some very small effect on the loading time BUT I agree...that's the last thing what someone should look for in a page optimization...for example Opera and IE doesn't use this property at all...nor search engine crawlers ;)

This seems to be more of a collaboration of other material as opposed to a helpful article. Looking at all the suggestions it's hard to work out what bottleneck you are actually trying to reduce. Server Runtime? Bandwidth? Browser-Rendering? In improving one, you're likely to worsen another.

- You need to explain those htaccess improvements, for one the 2 different "hacks" will simply over ride each other in some way, they may even over ride other elements if the user is unfamiliar with .htaccess and just overwrites their valuable vbSEO htaccess. You might want to mention that the .htaccess rules here (http://davidmchenry.info/2009/12/18/vbulletin-4-optimized-htaccess/)will make users cache everything for AGES; meaning if you edit a style once applying them, returning users won't ever see any updates you've made unless they do a cache refresh (ctrl + f5). Don't get me wrong, those caching parameters are pretty amazing at doing their job, props to the author.

- I agree with others, removing CSS rounded corners will only speed up browser-rendering and in new browsers possibly not even that much - actually not even at all in Internet Explorer.

- To be effective, you need to come up with ways to speed up your forum without turning loads of features off :(

- It's clear that vb4 is actually quite server intensive, so that's what needs to be worked on for most things. Some of those mods, like the "super charged" mod you mention actually ADDS processes in that it minifies the CSS/JS to save bandwith, they'll download faster sure, but there are now extra things running on an already bogged down server. The "download faster" argument is actually pretty invalid with the above .htaccces caching rules!

- This:
<META http-equiv=Page-Exit content=BlendTrans(Duration=0)>
<META http-equiv=Page-Enter content=BlendTrans(Duration=0)>
Doesn't actually do much either! It only works in IE and and isn't even properly formed HTMl.

All in all this is a really low quality article.

Some of it is really important stuff. I think rounded corners may slow down page rendering on very slow, outdated computers. The real problem with vbulletin is the amount of requests generated by styling and inefficient coding. All those icons, gradients, separate javascripts and css files are being loaded from one server. Take a look at yslow and see the numbers...
I have no idea why it wasn't addressed properly by the dev team (single css, single javascript! try using css sprites for the images). It was released in 2009 for ... sake! We all know the impact of number of requests on page rendering time...
So... Use CDN for static files delivery where possible. Try spreading out between a couple of subdomains. You can have one amazon s3 bucket with multiple cloudfront subdomains (ie. static1. static2. etc). In StyleVars there is a section where you define image paths - put the whole link to CF there (http including). When uploading to s3 - remember to set your expiration dates properly. This will help with consecutive page loads. Setting the header is not easy, but it is possible.
As for javascript and css optimization - I'm still looking for a solution. I've tried supercharge but I'm afraid it breaks a little too much...

wow
thanks a lot
nice collection

vbulletin 4 is so slow omg... i thought moving from 3.8 to 4 would be a big improvement but its seems they are going backwards in some areas... thanks for the tut but we shouldn't have to do this on a new product, its like getting a fast car but first take off all the windows doors and accessories before you can use it lol
My users are not impressed is ipboard a better option?:down:

vbulletin 4 is so slow omg... i thought moving from 3.8 to 4 would be a big improvement but its seems they are going backwards in some areas... thanks for the tut but we shouldn't have to do this on a new product, its like getting a fast car but first take off all the windows doors and accessories before you can use it lol
My users are not impressed is ipboard a better option?:down:
Ip Board, i haven't used it since maybe 08 ? But its a good software, you want a real forum? Stick with vBulletin :)
wow
thanks a lot
nice collection

I know its bad.

Thanks

Added a few options to the article.

Turned on the mem cache fetaure to file. Will keep an eye on this.

Also have all pictures/avatars/profile pic/attachments stored to file system.

CSS saved as files.

Anything else to consider?

Add some info to the article on the bottom, install OptiPNG :)

Some of this stuff may have some impact.

However, I still feel a lot of this has to do with client side and server side.

On the server side, there are a lot of people who are hosting their sites with big over-crowded shared hosting companies.

Consider this: when you got Windows 7, did you still run it on the same PC that ran Windows XP? no is most likely your answer.

Upgrade your host or your server - get them to tell you their server specs, and how many other users are sharing your server.

The client side stuff: Safari is the faster of the mainstream browsers to date. I've check VB4 in Safari, and am impressed with it's speed. No major issues vs VB3.8.

Ip Board, i haven't used it since maybe 08 ? But its a good software, you want a real forum? Stick with vBulletin :)


I know its bad.

sometimes we don't think about who is writing this stuff in here, chop suey was only 16 or 17, some of the critic of this article is a little harsh, now looking back on his suicide its easier to see he had issues, with criticism.

I know its bad

I bought vb_optimizer pro and done with it. lol
it have saved me 98,000 queries in 2 days :D

how do you edit "additional.css"?

4. Get rid of those rounded corners! Credit to Andy (http://www.vbulletin.org/forum/member.php?u=42356), original post here (http://www.vbulletin.org/forum/showpost.php?p=1991857&postcount=9).
One reason vB4 is slower than vb3 is the use of shading and rounded corners. Add this to the bottom of the additional.css template and your forum will speed up considerably.

* { -moz-box-shadow: none !important; }
* { -webkit-box-shadow: none !important; }

* { -moz-border-radius: 0px !important; }
* { -webkit-border-radius: 0px !important; }Feedback from users, saying their forum loads faster.


Measurements with Firebug showed no speed increase after removing the rounded corners.
It is a browser site rendering process and has nothing to do with the page request so the "speed effect" totally depends on the hardware specs of the visitor.

Hi there

In an effort to speed up my site, I stored css sheets as files.

However when I do that, my backgound image (in doc_background) doesn't work.

If I switch back to not storing css as files...the background image works again.

Anyway I can store css as files and still keep my background image?

Thanks

Cheers

no one?? :confused::eek:

To the top....still have this problem...anyone else?

tagged

Any new code for step 6 "vBulletin 4 optimize htaccess"?

Yes there is in my guide :P

I selected to store CSS as files and then all my editor icons disappeared.. I turned off store CSS as files and my editor buttons are back. I'd love to use this function, but gotta have the editor buttons. The button is there, and if you put your mouse over a button, the text says what it is, but the actual icon is whats gone.










privacy (GDPR)