Small Review of BUYVM KVM SLICE 512 Luxembourg

debaser

@psb777 said:
I think there should be a caveat that the IPv6 on BuyVM Lux is tunneled, despite on the site it claimed "Native IPV6 connectivity". Although in most cases it should be hassle-free thanks to pMTUd, users of VPN (for example Wireguard) have to manually adjust the MTU in order to avoid fragmented packets.

I saw that as well. It's tunneled via HE, but IPv6 traffic to Cogent seems native.

The same page states that the LUX datacenter has connections to 'major exchanges in Germany, France, and The Netherlands' and also 'Hurricane Electic, TeliaSonera, Level 3 Communications, PCCW Global'.

Information I get from the looking glass is that IPv4 always goes through Cogent and IPv6 is almost always tunneled via HE.net. So it's propably outdated information on this page. I'm sure Francisco or someone else can enlighten us.

It wouldn't be a dealbreaker for me, but routing through Cogent seems a bit suboptimal in some cases.

Francisco

@debaser said:

@psb777 said:
I think there should be a caveat that the IPv6 on BuyVM Lux is tunneled, despite on the site it claimed "Native IPV6 connectivity". Although in most cases it should be hassle-free thanks to pMTUd, users of VPN (for example Wireguard) have to manually adjust the MTU in order to avoid fragmented packets.

I saw that as well. It's tunneled via HE, but IPv6 traffic to Cogent seems native.

The same page states that the LUX datacenter has connections to 'major exchanges in Germany, France, and The Netherlands' and also 'Hurricane Electic, TeliaSonera, Level 3 Communications, PCCW Global'.

Information I get from the looking glass is that IPv4 always goes through Cogent and IPv6 is almost always tunneled via HE.net. So it's propably outdated information on this page. I'm sure Francisco or someone else can enlighten us.

It wouldn't be a dealbreaker for me, but routing through Cogent seems a bit suboptimal in some cases.

We have a little transit from root.lu, but scaling with them just wasn't a great option. Once we started to allow users to run TOR and such our usage went from sub 1Gbit to 4 - 5Gbit in peaks.

We have Cogent on site and are adding HE soon, I just have to finalize the cross connect over to LUX1.

It's not the most bitchin' EU network, but it's a pretty unique market and we provide a lot of bundled transit.

V6 is a combo of Cogent & HE's tables. Cogent covers 95%+ of the table with HE filling in for the rest.

Francisco

Daniel15

Any ETA for slices in Luxembourg? Looking to get a 512 but I haven't seen them in stock. @Francisco

VayVayKa

My first experience with KVM was with this offert.
There were few free bitcoins left and I decided why not. Took for a month.
In general, I was very pleased with the network, the hardware and (which is important) Law of the land.
I would love to use it further but I do not need a KVM (at its price) for my needs.

Daniel15 said: Looking to get a 512 but I haven't seen them in stock.

https://www.serverhunter.com/offer/buyvm-lu-e3-kvm-512mb/#stock_history

Daniel15

@VayVayKa said:
My first experience with KVM was with this offert.
There were few free bitcoins left and I decided why not. Took for a month.
In general, I was very pleased with the network, the hardware and (which is important) Law of the land.
I would love to use it further but I do not need a KVM (at its price) for my needs.

Daniel15 said: Looking to get a 512 but I haven't seen them in stock.

https://www.serverhunter.com/offer/buyvm-lu-e3-kvm-512mb/#stock_history

Thanks for the link. Seems like I just missed out! I want to try out the anycast functionality - I've got a slice in Vegas and New York, just not yet in Luxembourg.

Daniel15

Looks like there's some new stock this morning - Going to try it out

VayVayKa

Daniel15 said: Going to try it out

Its time to try.
83 is in stock right now
https://my.frantech.ca/cart.php?a=confproduct&i=1

Francisco

Just added a batch of new nodes this morning. Got a few more to rack up next week.

Once these are out the next big batch of stock will be in the spring when Slabs arrive.

Francisco

VayVayKa

Francisco said: Just added a batch of new nodes this morning. Got a few more to rack up next week.

Awesome!

VayVayKa said: https://my.frantech.ca/cart.php?a=confproduct&i=1

correct link
https://my.frantech.ca/cart.php?a=add&pid=1441

Daniel15

Francisco said: Just added a batch of new nodes this morning.

Do newer nodes have better hardware than older ones, or are they all the same?

Francisco

@Daniel15 said:

Francisco said: Just added a batch of new nodes this morning.

Do newer nodes have better hardware than older ones, or are they all the same?

All the same.

The DC has just been super busy on some projects on their end so they didn't finish racking things.

We've been reorganizing our original rack in LU which has required Anthony & I shuffle some users around so we can decommission it.

Francisco

cpsd

Well, after thinking for a long time, I bought my first slice & slab today Thanks.

partymonger

How does the performance compare to comparative Vultr plan?

willie

The closest vultr plan spec-wise is 512mb ram, 10gb ssd, 1 ipv4, and $3.50/m which is over 2x as expensive as a $20/y plan if you keep it all year. So I'd say it's not exactly a competing product. The vultr VM that I really like is the 1gb high frequency vm with 32gb ssd at $6/m. But again the 1gb buyvm slice is $3.50/m and while its cpu is slower, it has slab storage available and that makes the product a lot more interesting imho.

partymonger

@willie said:
The closest vultr plan spec-wise is 512mb ram, 10gb ssd, 1 ipv4, and $3.50/m which is over 2x as expensive as a $20/y plan if you keep it all year. So I'd say it's not exactly a competing product. The vultr VM that I really like is the 1gb high frequency vm with 32gb ssd at $6/m. But again the 1gb buyvm slice is $3.50/m and while its cpu is slower, it has slab storage available and that makes the product a lot more interesting imho.

Im using the 1gb from vultr. Its 5$. I havent found a better VFM yet in years.

ofit

I'm got back to the ship. Cpu score good (even better that was, may be it because of debian 10 or @Francisco did some optimizations ) but why OpenVPN network became worse? Debian 10 64 bit Angristan OpenVPN Script

pavel@pavel-envy6:~$ iperf3 -c 10.8.0.1 -t40 -p** -R                                                                                
Connecting to host 10.8.0.1, port **                                                                                                
Reverse mode, remote host 10.8.0.1 is sending                                                                                         
[  4] local 10.8.0.3 port 51848 connected to 10.8.0.1 port **                                                                       
[ ID] Interval           Transfer     Bandwidth                                                                                       
[  4]   0.00-1.00   sec  1.95 MBytes  16.4 Mbits/sec                                                                                  
[  4]   1.00-2.00   sec  5.51 MBytes  46.2 Mbits/sec                                                                                  
[  4]   2.00-3.00   sec  4.74 MBytes  39.8 Mbits/sec                                                                                  
[  4]   3.00-4.00   sec  4.97 MBytes  41.7 Mbits/sec                                                                                  
[  4]   4.00-5.00   sec  5.19 MBytes  43.5 Mbits/sec                                                                                  
[  4]   5.00-6.00   sec  4.61 MBytes  38.6 Mbits/sec                                                                                  
[  4]   6.00-7.00   sec  4.76 MBytes  39.9 Mbits/sec                                                                                  
[  4]   7.00-8.00   sec  4.40 MBytes  36.9 Mbits/sec                                                                                  
[  4]   8.00-9.00   sec  4.20 MBytes  35.2 Mbits/sec                                                                                  
[  4]   9.00-10.00  sec  4.50 MBytes  37.8 Mbits/sec                                                                                  
[  4]  10.00-11.00  sec  4.81 MBytes  40.3 Mbits/sec                                                                                  
[  4]  11.00-12.00  sec  5.19 MBytes  43.5 Mbits/sec                                                                                  
[  4]  12.00-13.00  sec  5.08 MBytes  42.6 Mbits/sec                                                                                  
[  4]  13.00-14.00  sec  4.61 MBytes  38.7 Mbits/sec                                                                                  
[  4]  14.00-15.00  sec  5.07 MBytes  42.5 Mbits/sec                                                                                  
[  4]  15.00-16.00  sec  5.37 MBytes  45.0 Mbits/sec                  
[  4]  16.00-17.00  sec  5.49 MBytes  46.1 Mbits/sec                  
[  4]  17.00-18.00  sec  5.43 MBytes  45.5 Mbits/sec                  
[  4]  18.00-19.00  sec  4.91 MBytes  41.2 Mbits/sec                  
[  4]  19.00-20.00  sec  5.07 MBytes  42.6 Mbits/sec                  
[  4]  20.00-21.00  sec  5.49 MBytes  46.1 Mbits/sec                  
[  4]  21.00-22.00  sec  5.05 MBytes  42.4 Mbits/sec                  
[  4]  22.00-23.00  sec  4.66 MBytes  39.1 Mbits/sec                  
[  4]  23.00-24.00  sec  4.11 MBytes  34.5 Mbits/sec                  
[  4]  24.00-25.00  sec  3.93 MBytes  33.0 Mbits/sec                  
[  4]  25.00-26.00  sec  4.31 MBytes  36.2 Mbits/sec                  
[  4]  26.00-27.00  sec  4.56 MBytes  38.2 Mbits/sec                  
[  4]  27.00-28.00  sec  4.92 MBytes  41.3 Mbits/sec                  
[  4]  28.00-29.00  sec  5.19 MBytes  43.5 Mbits/sec                  
[  4]  29.00-30.00  sec  5.52 MBytes  46.3 Mbits/sec                  
[  4]  30.00-31.00  sec  5.55 MBytes  46.6 Mbits/sec                  
[  4]  31.00-32.00  sec  4.68 MBytes  39.2 Mbits/sec                  
[  4]  32.00-33.00  sec  4.09 MBytes  34.3 Mbits/sec                  
[  4]  33.00-34.00  sec  4.30 MBytes  36.0 Mbits/sec                  
[  4]  34.00-35.00  sec  4.62 MBytes  38.8 Mbits/sec                  
[  4]  35.00-36.00  sec  5.00 MBytes  42.0 Mbits/sec                  
[  4]  36.00-37.00  sec  5.39 MBytes  45.2 Mbits/sec                  
[  4]  37.00-38.00  sec  5.67 MBytes  47.6 Mbits/sec                  
[  4]  38.00-39.00  sec  5.97 MBytes  50.1 Mbits/sec                  
[  4]  39.00-40.00  sec  5.33 MBytes  44.7 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-40.00  sec   195 MBytes  40.9 Mbits/sec  150             sender
[  4]   0.00-40.00  sec   194 MBytes  40.8 Mbits/sec                  receiver

iperf Done.

Francisco

Can you test without the vpn to compare?

Francisco

ofit

yes

root@home-server:~# iperf3 -c 104.244.**.** -t40 -p** -R 
Connecting to host 104.244.**.**, port **
Reverse mode, remote host 104.244.**.** is sending
[  5] local 192.168.1.2 port 34460 connected to 104.244.**.** port **
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  4.19 MBytes  35.1 Mbits/sec                  
[  5]   1.00-2.00   sec  13.8 MBytes   115 Mbits/sec                  
[  5]   2.00-3.00   sec  24.0 MBytes   201 Mbits/sec                  
[  5]   3.00-4.00   sec  11.8 MBytes  98.6 Mbits/sec                  
[  5]   4.00-5.00   sec  9.18 MBytes  77.0 Mbits/sec                  
[  5]   5.00-6.00   sec  9.82 MBytes  82.4 Mbits/sec                  
[  5]   6.00-7.00   sec  10.3 MBytes  86.2 Mbits/sec                  
[  5]   7.00-8.00   sec  10.4 MBytes  87.1 Mbits/sec                  
[  5]   8.00-9.00   sec  10.3 MBytes  86.4 Mbits/sec                  
[  5]   9.00-10.00  sec  10.8 MBytes  90.8 Mbits/sec                  
[  5]  10.00-11.00  sec  11.2 MBytes  94.0 Mbits/sec                  
[  5]  11.00-12.00  sec  11.7 MBytes  98.5 Mbits/sec                  
[  5]  12.00-13.00  sec  11.8 MBytes  99.1 Mbits/sec                  
[  5]  13.00-14.00  sec  12.5 MBytes   105 Mbits/sec                  
[  5]  14.00-15.00  sec  12.9 MBytes   108 Mbits/sec                  
[  5]  15.00-16.00  sec  13.6 MBytes   114 Mbits/sec                  
[  5]  16.00-17.00  sec  14.9 MBytes   125 Mbits/sec                  
[  5]  17.00-18.00  sec  10.7 MBytes  90.1 Mbits/sec                  
[  5]  18.00-19.00  sec  9.57 MBytes  80.3 Mbits/sec                  
[  5]  19.00-20.00  sec  10.5 MBytes  88.4 Mbits/sec                  
[  5]  20.00-21.00  sec  10.7 MBytes  89.9 Mbits/sec                  
[  5]  21.00-22.00  sec  10.9 MBytes  91.6 Mbits/sec                  
[  5]  22.00-23.00  sec  11.0 MBytes  92.0 Mbits/sec                  
[  5]  23.00-24.00  sec  11.0 MBytes  92.2 Mbits/sec                  
[  5]  24.00-25.00  sec  11.8 MBytes  98.6 Mbits/sec                  
[  5]  25.00-26.00  sec  11.8 MBytes  99.2 Mbits/sec                  
[  5]  26.00-27.00  sec  12.5 MBytes   105 Mbits/sec                  
[  5]  27.00-28.00  sec  13.0 MBytes   109 Mbits/sec                  
[  5]  28.00-29.00  sec  13.0 MBytes   109 Mbits/sec                  
[  5]  29.00-30.00  sec  11.4 MBytes  96.0 Mbits/sec                  
[  5]  30.00-31.00  sec  11.5 MBytes  96.2 Mbits/sec                  
[  5]  31.00-32.00  sec  12.0 MBytes   100 Mbits/sec                  
[  5]  32.00-33.00  sec  9.82 MBytes  82.4 Mbits/sec                  
[  5]  33.00-34.00  sec  10.2 MBytes  85.3 Mbits/sec                  
[  5]  34.00-35.00  sec  10.6 MBytes  89.1 Mbits/sec                  
[  5]  35.00-36.00  sec  11.4 MBytes  95.4 Mbits/sec                  
[  5]  36.00-37.00  sec  10.9 MBytes  91.4 Mbits/sec                  
[  5]  37.00-38.00  sec  11.2 MBytes  93.7 Mbits/sec                  
[  5]  38.00-39.00  sec  11.6 MBytes  97.3 Mbits/sec                  
[  5]  39.00-40.00  sec  11.9 MBytes   100 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-40.04  sec   465 MBytes  97.4 Mbits/sec  2693             sender
[  5]   0.00-40.00  sec   462 MBytes  96.9 Mbits/sec                  receiver

iperf Done.

Francisco

Could be the cipher you're using. I would make sure you have your cpu set to intel and the networking to virtio.

Francisco

jbuggie

I have a 512MB slice in Las Vegas with a slab for back up. Idle most of the time but when the back up ran, I've noticed pretty significant "steal time". CPU usage would be around 30-40% while steal time is in the 45-50%. It's pretty packed, I guess.

Francisco

@jbuggie said:
I have a 512MB slice in Las Vegas with a slab for back up. Idle most of the time but when the back up ran, I've noticed pretty significant "steal time". CPU usage would be around 30-40% while steal time is in the 45-50%. It's pretty packed, I guess.

More likely you're CPU rate limited.

You can ticket and I can check. I've had to lock down some nodes due to spikes but have been bable to back it off since.

Francisco

jbuggie

I'll open a ticket @Francisco, thanks. The back up ran for avg 15 min a day, with CPU peaking at around 30-50%. I'm not sure how it landed on CPU rate limited. It could be the inital back up that took a bit more than an hour and CPU peaked at 85-90%.

Francisco

@jbuggie said:
I'll open a ticket @Francisco, thanks. The back up ran for avg 15 min a day, with CPU peaking at around 30-50%. I'm not sure how it landed on CPU rate limited. It could be the inital back up that took a bit more than an hour and CPU peaked at 85-90%.

Sure. I'll check it out

Francisco

ofit

@Francisco said:
Could be the cipher you're using. I would make sure you have your cpu set to intel and the networking to virtio.

Francisco

There were defaults configs for Slice and OpenVPN.
I changed Ethernet Driver from Intel PRO/1000 to VIRTIO. Now everything ok. Thanks.

pavel@pavel-envy6:~$ iperf3 -c 10.8.0.1 -t40 -R -p**
Connecting to host 10.8.0.1, port **
Reverse mode, remote host 10.8.0.1 is sending
[  4] local 10.8.0.3 port 54352 connected to 10.8.0.1 port **
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec  2.61 MBytes  21.9 Mbits/sec                  
[  4]   1.00-2.00   sec  6.88 MBytes  57.7 Mbits/sec                  
[  4]   2.00-3.00   sec  10.8 MBytes  90.2 Mbits/sec                  
[  4]   3.00-4.00   sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]   4.00-5.00   sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]   5.00-6.00   sec  9.65 MBytes  80.9 Mbits/sec                  
[  4]   6.00-7.00   sec  11.2 MBytes  94.1 Mbits/sec                  
[  4]   7.00-8.00   sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]   8.00-9.00   sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]   9.00-10.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  10.00-11.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  11.00-12.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  12.00-13.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  13.00-14.00  sec  10.8 MBytes  90.4 Mbits/sec                  
[  4]  14.00-15.00  sec  10.8 MBytes  90.3 Mbits/sec                  
[  4]  15.00-16.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  16.00-17.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  17.00-18.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  18.00-19.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  19.00-20.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  20.00-21.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  21.00-22.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  22.00-23.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  23.00-24.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  24.00-25.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  25.00-26.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  26.00-27.00  sec  8.94 MBytes  75.0 Mbits/sec                  
[  4]  27.00-28.00  sec  12.6 MBytes   106 Mbits/sec                  
[  4]  28.00-29.00  sec  10.8 MBytes  90.5 Mbits/sec                                                                                  
[  4]  29.00-30.00  sec  10.8 MBytes  90.5 Mbits/sec                                                                                  
[  4]  30.00-31.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  31.00-32.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  32.00-33.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  33.00-34.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  34.00-35.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  35.00-36.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  36.00-37.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  37.00-38.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  38.00-39.00  sec  10.8 MBytes  90.5 Mbits/sec                  
[  4]  39.00-40.00  sec  10.8 MBytes  90.5 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-40.00  sec   422 MBytes  88.5 Mbits/sec  2021             sender
[  4]   0.00-40.00  sec   420 MBytes  88.0 Mbits/sec                  receiver

iperf Done.

About Block Storage Slabs
I thought Block Storage Slabs could be connected to any KVM Slices, but it only works with Las Vegas KVM Slices. Bad news for me, but I was very much surprised at seeing network speed for Las Vegas KVM Slices. How did you get that speed across half the world? You are really amazing. But of course the ping is high.

root@home-server:~# wget -O /dev/null http://speedtest.lv.buyvm.net/1000MB.test
--2019-09-12 12:50:50--  http://speedtest.lv.buyvm.net/1000MB.test
Распознаётся speedtest.lv.buyvm.net (speedtest.lv.buyvm.net)… 209.141.56.135, 2605:6400:20:78::1
Подключение к speedtest.lv.buyvm.net (speedtest.lv.buyvm.net)|209.141.56.135|:80... соединение установлено.
HTTP-запрос отправлен. Ожидание ответа… 301 Moved Permanently
Адрес: https://speedtest.lv.buyvm.net/1000MB.test [переход]
--2019-09-12 12:50:50--  https://speedtest.lv.buyvm.net/1000MB.test
Подключение к speedtest.lv.buyvm.net (speedtest.lv.buyvm.net)|209.141.56.135|:443... соединение установлено.
HTTP-запрос отправлен. Ожидание ответа… 200 OK
Длина: 1000000000 (954M) [application/octet-stream]
Сохранение в: «/dev/null»

/dev/null                         100%[===========================================================>] 953,67M  12,3MB/s    за 83s     

2019-09-12 12:52:15 (11,4 MB/s) - «/dev/null» сохранён [1000000000/1000000000]

root@home-server:~# ping 209.141.56.135
PING 209.141.56.135 (209.141.56.135) 56(84) bytes of data.
64 bytes from 209.141.56.135: icmp_seq=1 ttl=48 time=189 ms
64 bytes from 209.141.56.135: icmp_seq=2 ttl=48 time=190 ms
64 bytes from 209.141.56.135: icmp_seq=3 ttl=48 time=190 ms
64 bytes from 209.141.56.135: icmp_seq=4 ttl=48 time=189 ms
64 bytes from 209.141.56.135: icmp_seq=5 ttl=48 time=189 ms
64 bytes from 209.141.56.135: icmp_seq=6 ttl=48 time=189 ms
64 bytes from 209.141.56.135: icmp_seq=7 ttl=48 time=189 ms
^C
--- 209.141.56.135 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 14ms
rtt min/avg/max/mdev = 188.983/189.310/189.525/0.561 ms

ofit

But NY KVM Slice is not as fast as Las Vegas KVM Slices, although closer to my location. Ping better than Las Vegas KVM Slices.

root@home-server:~# ping 198.98.53.31
PING 198.98.53.31 (198.98.53.31) 56(84) bytes of data.
64 bytes from 198.98.53.31: icmp_seq=1 ttl=47 time=128 ms
64 bytes from 198.98.53.31: icmp_seq=2 ttl=47 time=129 ms
64 bytes from 198.98.53.31: icmp_seq=3 ttl=47 time=128 ms
64 bytes from 198.98.53.31: icmp_seq=4 ttl=47 time=128 ms
64 bytes from 198.98.53.31: icmp_seq=5 ttl=47 time=128 ms
^C
--- 198.98.53.31 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 9ms
rtt min/avg/max/mdev = 127.993/128.288/128.569/0.330 ms
root@home-server:~# wget -O /dev/null https://speedtest.ny.buyvm.net/1000MB.test
--2019-09-15 13:18:49--  https://speedtest.ny.buyvm.net/1000MB.test
Распознаётся speedtest.ny.buyvm.net (speedtest.ny.buyvm.net)… 198.98.53.31, 2605:6400:10:53::1
Подключение к speedtest.ny.buyvm.net (speedtest.ny.buyvm.net)|198.98.53.31|:443... соединение установлено.
HTTP-запрос отправлен. Ожидание ответа… 200 OK
Длина: 1000000000 (954M) [application/octet-stream]
Сохранение в: «/dev/null»

/dev/null                          41%[========================>                                   ] 398,80M  3,73MB/s    ост 2m 17s ^C

Francisco

ofit said: But NY KVM Slice is not as fast as Las Vegas KVM Slices, although closer to my location. Ping better than Las Vegas KVM Slices.

Working on NY stuff already

Francisco

ofit

@Francisco said:

ofit said: But NY KVM Slice is not as fast as Las Vegas KVM Slices, although closer to my location. Ping better than Las Vegas KVM Slices.

Working on NY stuff already

Francisco

Nice to hear it.

swat4

Hello everyone. A friend of mine does not have an account here so going through me.

He might be getting a slice in Las Vegas and he would like to know the host node info. Would you mind showing me the direction where I can find them please?

chocolateshirt

@swat4 said:
Hello everyone. A friend of mine does not have an account here so going through me.

He might be getting a slice in Las Vegas and he would like to know the host node info. Would you mind showing me the direction where I can find them please?

It is ryzen

swat4

@chocolateshirt said:

@swat4 said:
Hello everyone. A friend of mine does not have an account here so going through me.

He might be getting a slice in Las Vegas and he would like to know the host node info. Would you mind showing me the direction where I can find them please?

It is ryzen

Thank you for your help. I will let him know.