Response Times

[John Drew]

This morning I was on the iPod and seemed OK, but always a bit of a question mark on that device.
On the main computer now and did a number of page loads. I had been logged in for perhaps 10 minutes on idle and then did some checks:
17 secs to What's new, then 6,4,6,4 seconds for the next efforts to various messages. So if there is a problem it's not at your end now, the 17 sec delay may be while the internet got the path sorted out.
John

Hi, its great to see you visiting our forum. Why not try Proton Compiler for FREE? Download the FREE version of Proton Compiler, Its called Amicus18 and its available from HERE Already using proton Compiler??? Get rid of these pesky messages... get LICENSED USER STATUS

[hadv215]

Slow in the Netherlands. At least slower than it used to be. The main site is not bad, but What's new is terribly slow. Items there are not bad.

[Cruster]

Slow here, especially the what's new section.

[Lester]

I'm seeing very variable responses for users in different parts of the globe

I question, is the forum slow to respond,

some say yes

some say no

some say yesterday was bad, but today is ok

its difficult for me to know if there is an issue or not

the cache issue is no longer, so if the forum is slow now. Its some other issue.

your feedback is welcome.

[Lester]

vBulletin 4 has an internal database based cache that never cleans itself up (don't ask me why). Expired cache items will stay in the database indefinitely, ultimately slowing down the response times as the cache is read before each new request!!!!!
We now run a cron job that clears cache items that are expired/unused on an hourly basis

[joesaliba]

Lester,

This morning is super fast!

[hadv215]

quite a difference Lester, good job!

[pverburg]

Looking good I think you found the problem I use the what's new section all the time and that's fast now used to be slow.
Well done.
Paul V.

[John Drew]

"What's new" is currently running at 3 seconds for a new page load once a message is read.
John in Oz

[Lester]

The cache is supposed to speed up page loads by serving pre-stored pages based upon pages that have been previously requested.

Its ironic that the cache grew so large that reading through it to identify if the currently selected pages were in the cache or had to be served fresh, slowed down the serving of the requested page.

you just have to laugh :-)