FUMBBL :: Online Blood Bowl League

Joined: Aug 19, 2009

Posted: Sep 09, 2010 - 10:23

I think it would be a good idea to do a path ping instead of a tracert and ping as it provides more data. Could you do this next time it is running slow?
To do it you need to go to the commnad prompt and type:

pathping -n fumbbl.com

_________________

Christer

Joined: Aug 02, 2003

Posted: Sep 09, 2010 - 10:35

FUMBBL Staff

Another possibility would be that the game server is not handling the amount of games being played very well. Me and Kalimar haven't been able to run high-load tests to any significant extent. Therefore, here are a few more things you can look into when it happens:

1. Check the number of FFB games being played (Games Page)
2. Ask others who are playing FFB games if the game is slow for them
3. Check the Server status page to see if any of the servers are running at high CPU (note that Borak, the database server, run high early morning (BB time) to do backups. This should not have any effect on games being played.
4. Compare in-game pingtimes to your network ping. The game ping is likely to be a bit higher, but should reasonably close.

Prez

Joined: Aug 02, 2003

Posted: Sep 09, 2010 - 12:22

I played a game this morning from 0915-1130, took approx 1hr 15mins I think this has been my quickest game on FFB todate. In the first half I ran three Pathping cmds (results below. The game was quicker in the first half and towards the end things were beginning to slow noticeable, think my opponent had lag problem as well, but he described to me as his screen was frozen! Sounds similar to me.

I checked how many other games were playing at the end of the game:
6 FFB games
1 L
4 Ranked

Tracing route to fumbbl.com [213.64.182.36]
over a maximum of 30 hops:
0 192.168.1.2
1 192.168.1.1
2 89.241.64.1
3 62.24.254.218
4 62.24.254.139
5 78.151.225.9
6 62.24.240.6
7 78.144.0.208
8 79.141.38.133
9 213.248.83.53
10 80.91.252.205
11 80.91.250.220
12 213.248.64.29
13 80.91.254.117
14 80.91.247.97
15 81.228.94.74
16 81.228.79.216
17 81.228.79.190
18 213.64.182.36

Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.2
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1 0/ 100 = 0% |
2 29ms 0/ 100 = 0% 0/ 100 = 0% 89.241.64.1 0/ 100 = 0% |
3 40ms 0/ 100 = 0% 0/ 100 = 0% 62.24.254.21 0/ 100 = 0% |
4 40ms 0/ 100 = 0% 0/ 100 = 0% 62.24.254.139 0/ 100 = 0% |
5 43ms 0/ 100 = 0% 0/ 100 = 0% 78.151.225.9 0/ 100 = 0% |
6 49ms 0/ 100 = 0% 0/ 100 = 0% 62.24.24 0/ 100 = 0% |
7 48ms 0/ 100 = 0% 0/ 100 = 0% 78.144.0.208 0/ 100 = 0% |
8 47ms 0/ 100 = 0% 0/ 100 = 0% 79.141.38.133 0/ 100 = 0% |
9 46ms 0/ 100 = 0% 0/ 100 = 0% 213.248.83.53 0/ 100 = 0% |
10 49ms 0/ 100 = 0% 0/ 100 = 0% 80.91.252.205 0/ 100 = 0% |
11 69ms 0/ 100 = 0% 0/ 100 = 0% 80.91.250.220 0/ 100 = 0% |
12 83ms 0/ 100 = 0% 0/ 100 = 0% 213.248.64.29 0/ 100 = 0% |
13 81ms 0/ 100 = 0% 0/ 100 = 0% 80.91.254.11 0/ 100 = 0% |
14 80ms 0/ 100 = 0% 0/ 100 = 0% 80.91.247.9 0/ 100 = 0% |
15 80ms 0/ 100 = 0% 0/ 100 = 0% 81.228.94.74 0/ 100 = 0% |
16 80ms 0/ 100 = 0% 0/ 100 = 0% 81.228.79.216 0/ 100 = 0% |
17 79ms 0/ 100 = 0% 0/ 100 = 0% 81.228.79.190 0/ 100 = 0% |
18 81ms 0/ 100 = 0% 0/ 100 = 0% 213.64.182.36

Trace complete.

C:\>
C:\>
C:\>pathping -n fumbbl.com

Tracing route to fumbbl.com [213.64.182.36]
over a maximum of 30 hops:
0 192.168.1.2
1 192.168.1.1
2 89.241.64.1
3 62.24.254.218
4 62.24.254.139
5 78.151.225.9
6 62.24.240.6
7 78.144.0.208
8 79.141.38.133
9 213.248.83.53
10 80.91.252.205
11 80.91.250.220
12 80.91.247.144
13 80.91.247.217
14 213.248.101.141
15 81.228.94.74
16 81.228.79.216
17 81.228.79.190
18 213.64.182.36

Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1. 0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1 0/ 100 = 0% |
2 29ms 0/ 100 = 0% 0/ 100 = 0% 89.241.64.1 0/ 100 = 0% |
3 40ms 0/ 100 = 0% 0/ 100 = 0% 62.24.254.218 0/ 100 = 0% |
4 40ms 0/ 100 = 0% 0/ 100 = 0% 62.24.254.139 0/ 100 = 0% |
5 41ms 0/ 100 = 0% 0/ 100 = 0% 78.151.225.9 0/ 100 = 0% |
6 49ms 0/ 100 = 0% 0/ 100 = 0% 62.24.240.6 0/ 100 = 0% |
7 47ms 0/ 100 = 0% 0/ 100 = 0% 78.144.0.208 0/ 100 = 0% |
8 49ms 0/ 100 = 0% 0/ 100 = 0% 79.141.38. 0/ 100 = 0% |
9 45ms 0/ 100 = 0% 0/ 100 = 0% 213.248.83.53 0/ 100 = 0% |
10 50ms 0/ 100 = 0% 0/ 100 = 0% 80.91.252.20 0/ 100 = 0% |
11 68ms 0/ 100 = 0% 0/ 100 = 0% 80.91.250.220 0/ 100 = 0% |
12 85ms 0/ 100 = 0% 0/ 100 = 0% 80.91.247.14 0/ 100 = 0% |
13 83ms 0/ 100 = 0% 0/ 100 = 0% 80.91.247.21 0/ 100 = 0% |
14 84ms 0/ 100 = 0% 0/ 100 = 0% 213.248.101.141 0/ 100 = 0% |
15 80ms 0/ 100 = 0% 0/ 100 = 0% 81.228.94.74 0/ 100 = 0% |
16 79ms 0/ 100 = 0% 0/ 100 = 0% 81.228.79.216 0/ 100 = 0% |
17 79ms 0/ 100 = 0% 0/ 100 = 0% 81.228.79.190 0/ 100 = 0% |
18 81ms 0/ 100 = 0% 0/ 100 = 0% 213.64.182.36

Trace complete.

C:\>pathping -n fumbbl.com

Tracing route to fumbbl.com [213.64.182.36]
over a maximum of 30 hops:
0 192.168.1.2
1 192.168.1.1
2 89.241.64.1
3 62.24.254.218
4 62.24.254.139
5 78.151.225.9
6 62.24.240.6
7 78.144.0.208
8 79.141.38.133
9 213.248.83.53
10 80.91.252.205
11 80.91.250.220
12 213.248.64.29
13 80.91.249.71
14 80.91.248.194
15 81.228.94.74
16 81.228.79.216
17 81.228.79.190
18 213.64.182.36

Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.2
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.10/ 100 = 0% |
2 29ms 0/ 100 = 0% 0/ 100 = 0% 89.241.64.10/ 100 = 0% |
3 38ms 0/ 100 = 0% 0/ 100 = 0% 62.24.254.2 0/ 100 = 0% |
4 40ms 0/ 100 = 0% 0/ 100 = 0% 62.24.254.1390/ 100 = 0% |
5 43ms 0/ 100 = 0% 0/ 100 = 0% 78.151.225.90/ 100 = 0% |
6 48ms 0/ 100 = 0% 0/ 100 = 0% 62.24.240.60/ 100 = 0% |
7 49ms 0/ 100 = 0% 0/ 100 = 0% 78.144.0.208 0/ 100 = 0% |
8 47ms 0/ 100 = 0% 0/ 100 = 0% 79.141.38.133 0/ 100 = 0% |
9 47ms 0/ 100 = 0% 0/ 100 = 0% 213.248.83.5 0/ 100 = 0% |
10 49ms 0/ 100 = 0% 0/ 100 = 0% 80.91.252.2050/ 100 = 0% |
11 68ms 0/ 100 = 0% 0/ 100 = 0% 80.91.250.22 0/ 100 = 0% |
12 85ms 0/ 100 = 0% 0/ 100 = 0% 213.248.64.29 0/ 100 = 0% |
13 81ms 1/ 100 = 1% 1/ 100 = 1% 80.91.249.71 0/ 100 = 0% |
14 82ms 0/ 100 = 0% 0/ 100 = 0% 80.91.248.194 0/ 100 = 0% |
15 81ms 0/ 100 = 0% 0/ 100 = 0% 81.228.94.74 1/ 100 = 1% |
16 78ms 1/ 100 = 1% 0/ 100 = 0% 81.228.79.216 0/ 100 = 0% |
17 79ms 1/ 100 = 1% 0/ 100 = 0% 81.228.79.190 0/ 100 = 0% |
18 82ms 1/ 100 = 1% 0/ 100 = 0% 213.64.182.36

Trace complete.

C:\>

_________________
Prez

Garion

Joined: Aug 19, 2009

Posted: Sep 09, 2010 - 12:35

Hmm well the last path ping you did shows some packet loss. But only 1% on the final 3 hops. Which is nothing to do with your internet connection. So it seems more likely that the issues are either related to Java or possibly issues with the server which Christer has already asked us to to keep an eye on.

_________________

Prez

Joined: Aug 02, 2003

Posted: Sep 09, 2010 - 12:38

if i could work out how to successfully do a screen save of the server status, i'd put that up too. But is anyone else having these poroblems...I sort of gathered that others are not suffering. Most opponents I've played havent had the bad lag I get

_________________
Prez

Garion

Joined: Aug 19, 2009

Posted: Sep 09, 2010 - 12:45

I have experieced it too about 3 times, I have also been playing people who have been experiencing it before it a few times as well so I don't think it is just you. However it has been okay for the last 3 days for me.

_________________