Server load

My webhost disalbed my account because of Vbseo. They told me to disable it immidiately. Is there a way I can fix the setup for vbseo so I can can continue to use it without having my account disabled ?

Thanks

Hello Roger,

please open a support ticket here and include the information you got from your host.
Thank you.

i got the same problem

Im having this issue now as well. :( mines up to 150 tho :X

Replied to your support ticket.

My server load has spiked as well after install, about another 5 or so to load. I will say I have not tweaked the PHP.ini yet which I am about to do (was a apache reinstall that I was seeing how it performed on a base level before tweaking).

I just had to turn off VBSEO for my forum the load is so out of control. I am awaiting a response to my server tweak on the VB forum before I dare activate it again :(

Reporting the same here.

It's kicking my server's butt as opposed to before vbseo. I started noticing slower load times after install and checked my server resources finding this.

UserDomain%CPU%MEMMysql Processeshoopshoopstalk.net0.420.000.0 Top Process%CPU 7.5/usr/bin/php vbseo.php

Hello Deron,

please open a support ticket with ftp access to check this further.

UserDomain%CPU%MEMMysql Processeshoopshoopstalk.net0.420.000.0 Top Process%CPU 7.5/usr/bin/php vbseo.php

If you are using CGI version of PHP, all forum scripts load in processes list will be added to "vbseo.php" process since it calls vBulletin scripts (so, it's not only vBSEO processing time, but the full time vBSEO + vB ).

Are you all using Zend or Ioncube?

I am using Zend.

I must say, i am having also these issue's and opened a support ticket. The support is fast and good, but it hasn't resolved the problems off the big increase in load.

Running Zend and RC7 on a vb3.6.4.

Load goes easy 4 times higher when i enable vbseo.

Maybe it's a bug in vbseo? Now everyone is asked to open a ticket, but maybe it's an idea to get collectively some info what is causing the slowdown/increase in load?

Yeah the "open a ticket" response probably isn't suited here if you guys are thinking there's a bug in the latest few releases.

Maybe a "we are working on a solution to the issue" or "we are checking the code for issues" response might be better

Glad to see I'm not the only one with this issue but sorry you guys are having the problem too.