Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › Kimsufi Testing OVH
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Kimsufi Testing OVH

NeoonNeoon Community Contributor, Veteran
edited July 2013 in General

Hi,

I installed a CSS Server so you can Test our Ping and Performance (please also post it):
37.187.0.127:27015 Counter-Strike: Source
Please also tell me your Location, thanks.
I could add other Gameservers if you dont have Counter-Strike Source.

Thanks for Testing!

«13

Comments

  • taronyutaronyu Member

    What DC? GRA?

  • sundaymousesundaymouse Member

    Can I connect to it?

  • taronyutaronyu Member

    Also, I don't got it installed anymore. Would love to play against some LET members :P

  • sundaymousesundaymouse Member

    I connected to your dust2, and the ping from UK is not bad. ~45ms, I think it could handle a multiplayer game.

  • NeoonNeoon Community Contributor, Veteran

    Yeah its GRA

  • DomainBopDomainBop Member

    RBX to GRA

    2  rbx-g2-a9.fr.eu (91.121.128.45)  1.104 ms  1.196 ms  1.227 ms
 3  * * *
 4  gra-g2-a9.fr.eu (178.33.103.218)  7.837 ms  8.246 ms  8.339 ms
 5  gra-3b-6k.fr.eu (178.33.103.230)  7.022 ms * gra-3a-6k.fr.eu (178.33.103.226)  7.108 ms
 6  ks3323132.kimsufi.com (37.187.0.127)  7.146 ms  7.141 ms  7.170 ms
  • sundaymousesundaymouse Member
    edited July 2013

    Great, played with a random CT for two rounds, and it was totally playable. Looks like there'll be a cheap dedicated solution for CSS server.

  • NeoonNeoon Community Contributor, Veteran

    N2800 should keep about 20-32 Source Engine slots i think.

  • ZeroZero Member
    edited July 2013

    @sundaymouse So you was the one in game? :P Anyway, good ping from Italy 60 - 65

  • sundaymousesundaymouse Member

    I think it's the time for LET to have an offical CSS server now.

    Thanked by 1udk
  • sundaymousesundaymouse Member

    @Zero said:
    sundaymouse So you was the one in game? :P Anyway, good ping from Italy 60 - 65

    Yes, good.

  • xsetxset Member

    @domainbop ping looks good :) Seems that ping would be fine for running a 2/3 node backend cluster on KS16Gs @ GRA and 2 server frontend+1 backend @ RBX on mini-sps :) That's my plan if they deliver the 2 x KS16Gs for me next week.

  • ZeroZero Member

    Now it's lagging as hell...don't know whats happening

  • NeoonNeoon Community Contributor, Veteran

    DDOS or some Network Abuse.

  • xsetxset Member
    edited July 2013

    @zero weird. I guess their DDOS protection started working!

    From KS2G @ RBX

    PING ks3323132.kimsufi.com (37.187.0.127) 56(84) bytes of data.
From vac1-1-n7.fr.eu.firewall (178.33.100.152) icmp_seq=1 Time to live exceeded
From vac1-1-n7.fr.eu.firewall (178.33.100.152) icmp_seq=2 Time to live exceeded
From vac1-1-n7.fr.eu.firewall (178.33.100.152) icmp_seq=3 Time to live exceeded
From vac1-1-n7.fr.eu.firewall (178.33.100.152) icmp_seq=4 Time to live exceeded
From vac1-1-n7.fr.eu.firewall (178.33.100.152) icmp_seq=5 Time to live exceeded
From vac1-1-n7.fr.eu.firewall (178.33.100.152) icmp_seq=6 Time to live exceeded
^C
--- ks3323132.kimsufi.com ping statistics ---
6 packets transmitted, 0 received, +6 errors, 100% packet loss, time 5007ms

This was before:

Traceroute to 37.187.0.127 (37.187.0.127), 30 hops max, 60 byte packets
 1  vss-1-6k.fr.eu (94.23.27.253)  0.336 ms * *
 2  rbx-g1-a9.fr.eu (94.23.122.170)  4.900 ms  4.901 ms  4.867 ms
 3  * * *
 4  gra-g1-a9.fr.eu (178.33.103.216)  7.343 ms  7.606 ms  7.620 ms
 5  gra-3a-6k.fr.eu (178.33.103.224)  6.759 ms * *
 6  ks3323132.kimsufi.com (37.187.0.127)  7.614 ms  7.656 ms  7.479 ms

This is now:

traceroute to 37.187.0.127 (37.187.0.127), 30 hops max, 60 byte packets
 1  vss-1-6k.fr.eu (94.23.27.253)  18.880 ms * *
 2  rbx-g1-a9.fr.eu (94.23.122.170)  1.086 ms  1.340 ms  1.354 ms
 3  vac1-0-a9.fr.eu.vaccum (178.33.100.149)  1.239 ms  1.935 ms  2.268 ms
 4  vac1-1-n7.fr.eu.firewall (178.33.100.152)  1.784 ms  1.891 ms  2.003 ms
 5  vac1-2-n7.fr.eu (91.121.215.9)  0.558 ms  0.666 ms  0.769 ms
 6  vac1-3-n7.fr.eu (91.121.215.13)  0.975 ms  0.591 ms  0.637 ms
 7  10.21.50.42 (10.21.50.42)  0.498 ms * *
 8  91.121.131.255 (91.121.131.255)  0.893 ms  0.869 ms rbx-s6-6k.fr.eu (91.121.131.93)  0.930 ms
 9  vac1-0-a9.fr.eu.vaccum (178.33.100.149)  1.969 ms vac1-0-a9.fr.eu.vaccum (178.33.100.151)  2.367 ms  2.714 ms
10  vac1-1-n7.fr.eu.firewall (178.33.100.152)  0.508 ms  0.622 ms  1.600 ms
11  vac1-2-n7.fr.eu (91.121.215.9)  0.697 ms  0.679 ms  0.800 ms
12  vac1-3-n7.fr.eu (91.121.215.13)  0.855 ms  0.988 ms  1.088 ms
13  10.21.50.43 (10.21.50.43)  0.579 ms * *
14  91.121.131.255 (91.121.131.255)  3.179 ms  3.115 ms  3.033 ms
15  vac1-0-a9.fr.eu.vaccum (178.33.100.151)  2.297 ms vac1-0-a9.fr.eu.vaccum (178.33.100.149)  2.972 ms  3.280 ms
16  vac1-1-n7.fr.eu.firewall (178.33.100.152)  0.579 ms  0.561 ms  0.564 ms
17  vac1-2-n7.fr.eu (91.121.215.9)  0.769 ms  0.733 ms  0.557 ms
18  vac1-3-n7.fr.eu (91.121.215.13)  0.589 ms  0.672 ms  0.722 ms
19  * * *
20  91.121.131.255 (91.121.131.255)  2.323 ms rbx-s6-6k.fr.eu (91.121.131.93)  0.900 ms 91.121.131.255 (91.121.131.255)  2.300 ms
21  vac1-0-a9.fr.eu.vaccum (178.33.100.149)  2.459 ms  2.723 ms vac1-0-a9.fr.eu.vaccum (178.33.100.151)  4.620 ms
22  vac1-1-n7.fr.eu.firewall (178.33.100.152)  0.688 ms  0.660 ms  0.660 ms
23  vac1-2-n7.fr.eu (91.121.215.9)  0.800 ms  0.886 ms  0.966 ms
24  vac1-3-n7.fr.eu (91.121.215.13)  0.805 ms  0.897 ms  0.891 ms
25  * * *
26  91.121.131.255 (91.121.131.255)  0.995 ms rbx-s6-6k.fr.eu (91.121.131.93)  1.123 ms  0.964 ms
27  vac1-0-a9.fr.eu.vaccum (178.33.100.151)  2.281 ms vac1-0-a9.fr.eu.vaccum (178.33.100.149)  2.795 ms  2.853 ms
28  vac1-1-n7.fr.eu.firewall (178.33.100.152)  0.794 ms  0.755 ms  0.835 ms
29  vac1-2-n7.fr.eu (91.121.215.9)  0.746 ms  0.869 ms  0.871 ms
30  vac1-3-n7.fr.eu (91.121.215.13)  0.753 ms  0.759 ms  0.760 ms
  • NeoonNeoon Community Contributor, Veteran

    I also got a E-Mail about error on my Server, one minute later it says its fixed.

  • doughnetdoughnet Member

    ping was great for me in the us west!

  • xsetxset Member

    @infinity580 Can't ping your KS2G... are you sure it's fixed. Seems like its target of a DDOS? There's the OVH vacuum in operation according to traceroute. But at least protocol seems to be working, other than ICMP.

  • ZeroZero Member

    Oh, seems good then :)

  • jkr1711jkr1711 Member

    @sundaymouse Who's your ISP? Getting around 16-17ms ping with BT Infinity. Just curious...

  • NeoonNeoon Community Contributor, Veteran

    Added 37.187.0.127:27021 Team Fortress

  • rm_rm_ IPv6 Advocate, Veteran

    Can't ping your KS2G... are you sure it's fixed. Seems like its target of a DDOS? There's the OVH vacuum in operation according to traceroute. But at least protocol seems to be working, other than ICMP.

    Maybe high UDP packet rate from the game triggered their DDOS protection. Perhaps they still got a long way to go in tuning it so it doesn't have false alarms.

  • xsetxset Member

    @rm_ I can ping it outside OVH, but from OVH I get TTL exceeded. So vacuum seems to be operational at least for traffic inside OVH.

  • chaufferchauffer Member
    edited July 2013

    okay, TF2 up at 37.187.0.127:27021 not my server but I wouldn't mind if somebody joined, I wanna know if this thing can handle TF2 properly, maybe MVM?

    EDIT: disregard that, server owner disconnected

  • NeoonNeoon Community Contributor, Veteran
    edited July 2013

    No, still online... wating for yah

  • MaouniqueMaounique Host Rep, Veteran

    In cs1.6 many years ago i had 40 slots on a duron 900 overclocked to 1200. Worked lagless for the local loop and pretty well from within romania. I think a 4 threads atom will be able to host a source game. Even 2 threads, but fewer slots.

  • NeoonNeoon Community Contributor, Veteran
    edited July 2013

    Thanks for coming testing, on the big wave we got some little Laggs because one core was at 100% but it was running well the hole time. Some laggs at MVM are normal
    http://s7.directupload.net/file/d/3330/4cgad69k_png.htm
    http://s1.directupload.net/file/d/3330/h25zhims_png.htm
    Most time it was arround 60-70% one core.

  • AdducAdduc Member

    But that was with 3-4 players. How is it going to handle a 24-32 player server?

  • asterisk14asterisk14 Banned

    @sundaymouse said:
    I connected to your dust2, and the ping from UK is not bad. ~45ms, I think it could handle a multiplayer game.

    I get 41ms from near Leeds on Sky normal broadband.

    @jkr1711 said:
    sundaymouse Who's your ISP? Getting around 16-17ms ping with BT Infinity. Just curious...

    Seems like Sky is crap, I get around 37ms just to Manchester!

  • NeoonNeoon Community Contributor, Veteran
    edited July 2013

    aahhh you forgot lots of bots :D i think it should handle about 26 Slots each core.
    6 Players arround 20% one core CSS

Sign In or Register to comment.