VBSEO Server Intensive?

Well we have relations using vbSEO and recently updated theirs. The host had warned that vbSEO was hogging up the server and their account had to be disabled for sometime.

It was advised to move over to VPS or a dedicated server to handle such requests from vbSEO as it used up a lot of resources on a shared enviroment.

Could a staff member from vbSEO clarify this further please?

Cheers

vbseo does add a little resource over standard vbulletin.
I personally saw .1 load increase from standard vb to vbseo'ed vb.

but at the same time, 3.7 added .2 load average over 3.6



Hosts' tend to blame 'vbseo.php' as a huge resource hog because that's how vbseo works.... EVERY script gets processed through vbseo.php, thus, 'vbseo.php' looks like a huge resource hog compared to the rest of the files on your site, as they don't get called directly so to speak to share the useage percentage.

Originally Posted by briansol

vbseo does add a little resource over standard vbulletin.
I personally saw .1 load increase from standard vb to vbseo'ed vb.

but at the same time, 3.7 added .2 load average over 3.6

Hosts' tend to blame 'vbseo.php' as a huge resource hog because that's how vbseo works.... EVERY script gets processed through vbseo.php, thus, 'vbseo.php' looks like a huge resource hog compared to the rest of the files on your site, as they don't get called directly so to speak to share the useage percentage.

Correct me if im wrong but your saying that vb 3.7 alone uses up server resources more so than vb 3.6? I would assume so as they have installed some extra features, but i dont think that would be of much concern at the moment.

With regards to Host tend to blame vbseo... i dont think they tend to, but rather they do blame vbseo for the right reasons as youve quite rightly mentioned that every script gets processed through vbseo thus making vbseo look a huge resource gobbler...

So does that mean with new customers customers purchasing the new vb 3.7 and with previous customers who upgrade to vb 3.7 and use vbseo should be weary that their host might disable their account due to server resources being used up.

Take a look at what one technical support guy said in one of our tickets below:

"I am pasting below the stats from our resource monitoring:

Top Process %CPU 100 [php]
Top Process %CPU 48.0 [php]
Top Process %CPU 39.0 /usr/bin/php vbseo.php

As you can see, your site was using up to 100% of the available CPU resources - all of the CPU resources in a shared hosting environment.

You need a dedicated server for a site this heavy."

Does this mean then users are going to have to host on dedicated or semi dedicated servers in order to run vbseo... as far as i can see things any host on a shared account will be likely to disable your account if you hog up 100% of the system resources... think about it.. 50% alone is a lot and all the other poor customers on the same server having to suffer because one person is running an intensive script such as vbseo.

The host suggested a dedicated server which means spending anything from $80+ for a dedicated server as oppose to a shared server.

Originally Posted by hornstar6969

if your host wont allow vbseo and want to disable your account, then move to a host that is better.

Your missing the point. The host allows vbseo but its the system resources which is the problem. Not just this host but i think any host in their right mind wont allow a website which uses up almost 100% system resources...


I look forward to your replies.

I have a big board with a million posts, so i cannot even related to a shared environment.

going from 3.5.5 to 3.5.5 w/vbseo, i jumped about .1 in load average.
going from 3.6.8 w/vbseo to 3.7.0 w/vbseo i jumped .2 in load (and vbseo was unchanged, without re-writing the new 3.7 features)

My point i'm trying to make is that vb's version and new features caused more load than adding vbseo did.


To my original point that 'vbseo.php' uses a lot of resources:

in stock vb, showthread.php, forumdisplay.php and all the rest SHARE the use.
in vbseo mode, vbseo.php is the file that takes over as the 'parent' script, which thus includes/process the proper vb script from it

if your host is seeing something like
10% showthread.php
5% forumhome.php
3% forumdisplay.php
vs
18% vbseo.php

vbseo looks like a hog, but in reality, it's using the same amount of resources.



At the end of the day moving from being a normal load site where they never contacted you to claiming 100% cpu usage simply won't happen from vbseo alone. They over-sold the box, like they all do, and now they are trying to dictate what you can and can't do on the item you pay for.... which goes back to hornstar's post....

Moreover, shared hosting is just that... shared and designed for 'personal' and other low-traffic websites.... not high-traffic sites.

If you're getting some traffic, it may be time to upgrade to a VPS (which you can get for around $50-$150)



What's your foum look like?
total members, posts, avg online with 15 min cookie, record online, uniques per day, impressions per day?