The UK Babe Channels Forum

(05-05-2011 01:43 )HEX!T Wrote: [ -> ]after looking through tonights tracert data there is little or no indication of connection problems. some pings are a little high but that can be explained by the users location from there exchanges and general net trafic from the U.S..
the only other probable explanation is a bandwidth problem at the server when a 1000+ guests connect. so i guess that the site is using up its allocation at peak times. and theres nothing any 1 can do about that. its up to the server provider to allocate more bandwidth. another possible solution is admin may have to limit the amount of guests or prioritize members over guests. he may if he can, add a check that will auto kick multiple connections from the same ip.

I'm guessing the problem has little to do with bandwidth and it's more likely that there's an issue with the SQL server this forum runs on. It's probably just getting hammered with more queries than it's capable of dealing with, hence the fact it seems to always be on a go-slow.

thats a possibility especially if the server itself has a weak cpu. if its a reasonably fast dual or quad of 2.4 or better then that shouldn't be a problem as gaming servers handle higher loads on that kind of system.

although i look at it this morning and see a couple of 170+ up to 270+ this would explain why no 1 reported any time outs just slow connection. as the list shows no timeouts at all.

but lets keep it going and get a broader picture... thanx for the effort so far.

Hexit may be correct about it being a bandwidth problem.
I've just seen this recent post on the linux Mint blog, there have been problems with their repositories (where software is downloaded/updated from) due to bandwidth issues and too many users.

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\aceman65>tracert http://www.babeshows.co.uk

Tracing route to babeshows.co.uk []
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms api.home
2 279 ms 29 ms 29 ms 217.32.97.122
3 29 ms 28 ms 28 ms 217.32.97.145
4 37 ms 37 ms 36 ms 213.1.69.186
5 37 ms 36 ms 36 ms 213.120.157.18
6 37 ms 36 ms 36 ms 213.120.157.178
7 36 ms 60 ms 36 ms acc1-10GigE-1-3-0.mr.21cn-ipp.bt.net [109.159.250.86]
8 303 ms 47 ms 48 ms core1-te0-3-0-5.ealing.ukcore.bt.net [109.159.250.13]
9 43 ms 43 ms 43 ms core1-xe0-0-0.redbus.ukcore.bt.net [62.6.200.73]
10 292 ms 329 ms 292 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]
11 45 ms 44 ms 44 ms ge-3-0-0.mpr1.lhr2.uk.above.net [64.125.28.126]
12 116 ms 116 ms 116 ms so-1-1-0.mpr1.dca2.us.above.net [64.125.31.186]
13 117 ms 129 ms 117 ms xe-1-3-0.cr1.dca2.us.above.net [64.125.29.21]
14 143 ms 145 ms 144 ms xe-0-2-0.cr1.iah1.us.above.net [64.125.25.114]
15 143 ms 392 ms 143 ms xe-1-1-0.er1.iah1.us.above.net [64.125.26.222]
16 392 ms 144 ms 143 ms 209.66.99.94.available.above.net [209.66.99.94]
17 143 ms 144 ms 142 ms te2-6.dsr01.hstntx1.networklayer.com [207.218.245.30]
18 404 ms 358 ms 314 ms po16.dsr02.hstntx2.networklayer.com [70.87.253.105]
19 143 ms 143 ms 143 ms te4-1.car14.hstntx2.networklayer.com [74.55.252.222]
20 144 ms 143 ms 144 ms d2.57.7bae.static.theplanet.com [174.123.87.210]


Trace complete.

07-05-11 02:20

Seems horrendously slow at present. And after looking at these results, I can see why.


Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\aceman65>tracert http://www.babeshows.co.uk

Tracing route to babeshows.co.uk []
over a maximum of 30 hops:

1 1 ms <1 ms 258 ms api.home
2 288 ms 287 ms 287 ms 217.32.97.122
3 293 ms 286 ms 30 ms 217.32.97.145
4 295 ms 295 ms 294 ms 213.1.69.186
5 295 ms 294 ms 295 ms 213.120.157.18
6 296 ms 295 ms 295 ms 213.120.157.178
7 296 ms 294 ms 295 ms acc1-10GigE-1-3-0.mr.21cn-ipp.bt.net [109.159.250.86]
8 303 ms 306 ms 306 ms core1-te0-3-0-5.ealing.ukcore.bt.net [109.159.250.13]
9 302 ms 302 ms 302 ms core1-xe0-0-0.redbus.ukcore.bt.net [62.6.200.73]
10 302 ms 302 ms 302 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]
11 304 ms 304 ms 302 ms ge-3-0-0.mpr1.lhr2.uk.above.net [64.125.28.126]
12 375 ms 374 ms 376 ms so-1-1-0.mpr1.dca2.us.above.net [64.125.31.186]
13 396 ms 375 ms 375 ms xe-1-3-0.cr1.dca2.us.above.net [64.125.29.21]
14 403 ms 402 ms 402 ms xe-0-2-0.cr1.iah1.us.above.net [64.125.25.114]
15 402 ms 402 ms 402 ms xe-1-1-0.er1.iah1.us.above.net [64.125.26.222]
16 404 ms 403 ms 403 ms 209.66.99.94.available.above.net [209.66.99.94]
17 145 ms 403 ms 403 ms te2-6.dsr01.hstntx1.networklayer.com [207.218.245.30]
18 403 ms 404 ms 403 ms po16.dsr02.hstntx2.networklayer.com [70.87.253.105]
19 403 ms 144 ms 419 ms te4-1.car14.hstntx2.networklayer.com [74.55.252.222]
20 403 ms 403 ms 403 ms d2.57.7bae.static.theplanet.com [174.123.87.210]


Trace complete.

08-05-11 12:30

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

Tracing route to babeshows.co.uk []
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms Livebox-6090 []
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 163 ms 163 ms 161 ms d2.57.7bae.static.theplanet.com [174.123.87.210]


Trace complete.

It's really, really slow for me at present.

It became very very slow around 11.30am this morning. It was ok before then.
It stayed like that for me until just after 1pm when it then went back to normal.

Over the past few days I've found the forum really slow. I even got a white screen saying

Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

I've had a few similar errors but in general, it's just been extremely slow the past couple of weeks, today in particular.