Does the vBulletin call-to-home Slow the site down?

[gibigbig]

Every forum creates a ridiculous amount of traffic, it worries me that vbulletin's call to home feature which is required in the license agreement, may lag on the sheer mass of the internet's traffic. Large forums like Digitalpoint may be one of the best examples.

As my experience goes, the call to home is admin panel based, which means that only admins can actually initiate the call to home process, and that is a huge relief in itself, although, vBulletin's forums are increasingly being flowered all over cyberspace,. Ultimately the question still remains.

Will there be a future lag as the vBulletin's servers gets closer to its capacitance?

For those of you who don't know, a call -to-home is a request used to verify that the copy of vb being used is valid, im not sure on the details as to if this only occurs during installation or for any time you may log in the admincp.

[KW802]

OK, I'll ask...

As you say, the call home is only when you are connected to the ACP so how do you think that is slowing down your forums?

[gibigbig]

sorry for not explaining this is my above post, it can slow down a site because the call to home functions like this:

Page request ---> [call to home for permission] ---> [if ok, print page] if not [ print error ]

since the print process depends on the response from the third party server, if it is congested, the site will stall. I hope this explains my point better.

are the vbulletins servers up for this?

[KW802]

sorry for not explaining this is my above post, it can slow down a site because the call to home functions like this:


Page request ---> [call to home for permission] ---> [if ok, print page] if not [ print error ]

since the print process depends on the response from the third party server, if it is congested, the site will stall. I hope this explains my point better.

are the vbulletins servers up for this?
As you stated in your first post it is only in the ACP that the dial home is done, not when somebody is actually visiting your forums. In other words, if you visit your ACP once a day then there will be only one dial home done a day. If you visit once a month then only one dial home per month will be done. Normal page requests (eg: browsing your forums) does not create a dial home request.

[gibigbig]

i know but i went on to say:

although, vBulletin's forums are increasingly being flowered all over cyberspace,. Ultimately the question still remains.

and I'm always busy inside my admin panel, I make my own skins and plugins, and what not so my refresh button is abused. Im sure theres alot more out there like me, even though not the bulk of users are. I'm you can see my point.

[Paul M]

There is no call home on every page request. Its only in the ACP, on the index page.

[gibigbig]

yes we established that.

[Lynne]

Then would you understand that the only page it could slow down would be the index page in the admincp? It has no effect whatsoever on normal users on the forums.

[Boofo]

I notice no slowdown at all in the Admin CP index.php, and I am in there quite a bit working on products. So, yes, I guess you could say the vb servers are up to the challenge. ;)

[gibigbig]

I notice no slowdown at all in the Admin CP index.php, and I am in there quite a bit working on products. So, yes, I guess you could say the vb servers are up to the challenge. ;)

As a coder and designer, I was a bit worried if we all needed constant refreshing for our developments, if the server would show any lag.
Thank you for reading and understand with positive feedback.

[Digital Jedi]

Is a call home request more or less server intensive then, say, logging into and posting on vBulletin.org? I'm just saying, if both websites can handle the combined 19,000 active users on a daily basis, why would they not have resources able to handle any additional requests?