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

› › DATAWAGON | NEW AMD Epyc Milan VPS | 8GB RAM @ $6 | RAID10 NVMe | FREE Windows Server | FREE Backups - Page 3
New on LowEndTalk? Please Register and read our Community Rules.

DATAWAGON | NEW AMD Epyc Milan VPS | 8GB RAM @ $6 | RAID10 NVMe | FREE Windows Server | FREE Backups

13»

Comments

  • sayyikusayyiku Member

    @DataWagon said:

    @sayyiku said:

    @DataWagon said:

    @sayyiku said:

    I think your plan is too stupid.

    It's hard not to wonder if your server is going crazy with overselling.

    All you need to do is use more RAM, and more will be allocated. You are only using 1.2GB RAM, which is why you only have this much allocated by the balloon driver. The node you are on is already full, and no one has complained about performance. If you really want to see the 'total' RAM all the time, you can simply unload the balloon driver.

    Use the server however you intend and you'll see performance is exceptional in all aspects (which you can already see from all of the YABS that have been posted).

    Not really, you guys are severely compressing performance, I was able to use up to 4g-6g RAM before, and the CPU wouldn't even go to 100%. But now it's down to 2g RAM,CPU is consistently 100% and stability is terrible. My node-exporter can't even capture the data. docker app actually quits automatically.


    This has nothing to do with your the balloon driver?

    The CPU usage shouldn't have anything to do with balloon driver. Send a ticket and we will look into your issue, however you are also free to simply unload the balloon driver.

    Yabs benchmarking is really quality, but really after using this virtio_balloon module docker service is very unstable.
    After I disabled the module, docker went back to normal.

    Basic System Information:
---------------------------------
Uptime     : 0 days, 0 hours, 7 minutes
Processor  : AMD EPYC 7713 64-Core Processor
CPU cores  : 8 @ 1999.998 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM        : 15.6 GiB
Swap       : 0.0 KiB
Disk       : 77.6 GiB
Distro     : Debian GNU/Linux 11 (bullseye)
Kernel     : 5.10.0-25-amd64
VM Type    : KVM
IPv4/IPv6  : ✔ Online / ✔ Online

IPv6 Network Information:
---------------------------------
ISP        : DataWagon LLC
ASN        : AS27176 DataWagon LLC
Host       : DataWagon LLC
Location   : New York, New York (NY)
Country    : United States

fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 318.87 MB/s  (79.7k) | 4.10 GB/s    (64.0k)
Write      | 319.71 MB/s  (79.9k) | 4.12 GB/s    (64.4k)
Total      | 638.59 MB/s (159.6k) | 8.22 GB/s   (128.5k)
           |                      |                     
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 9.77 GB/s    (19.0k) | 2.31 GB/s     (2.2k)
Write      | 10.29 GB/s   (20.1k) | 2.46 GB/s     (2.4k)
Total      | 20.06 GB/s   (39.1k) | 4.77 GB/s     (4.6k)

iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 50.9 Mbits/sec  | 68.1 Mbits/sec  | 140 ms         
Scaleway        | Paris, FR (10G)           | busy            | busy            | 87.6 ms        
NovoServe       | North Holland, NL (40G)   | busy            | busy            | 146 ms         
Uztelecom       | Tashkent, UZ (10G)        | 301 Mbits/sec   | 296 Mbits/sec   | 230 ms         
Clouvider       | NYC, NY, US (10G)         | 394 Mbits/sec   | 812 Mbits/sec   | 74.6 ms        
Clouvider       | Dallas, TX, US (10G)      | 121 Mbits/sec   | 198 Mbits/sec   | 113 ms         
Clouvider       | Los Angeles, CA, US (10G) | 62.5 Mbits/sec  | 139 Mbits/sec   | 136 ms         

iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 21.1 Mbits/sec  | 33.7 Mbits/sec  | 140 ms         
Scaleway        | Paris, FR (10G)           | busy            | 281 Mbits/sec   | 154 ms         
NovoServe       | North Holland, NL (40G)   | busy            | busy            | 146 ms         
Uztelecom       | Tashkent, UZ (10G)        | 113 Mbits/sec   | 185 Mbits/sec   | 230 ms         
Clouvider       | NYC, NY, US (10G)         | 44.6 Mbits/sec  | 66.2 Mbits/sec  | 74.5 ms        
Clouvider       | Dallas, TX, US (10G)      | 24.7 Mbits/sec  | 64.0 Mbits/sec  | 113 ms         
Clouvider       | Los Angeles, CA, US (10G) | 16.0 Mbits/sec  | 45.7 Mbits/sec  | 136 ms         

Geekbench 6 Benchmark Test:
---------------------------------
Test            | Value                         
                |                               
Single Core     | 1416                          
Multi Core      | 7217                          
Full Test       | https://browser.geekbench.com/v6/cpu/2671525
    Thanked by 1amaeva080
  • nvmenvme Member

    @sayyiku said:

    @DataWagon said:

    @sayyiku said:

    @DataWagon said:

    @sayyiku said:

    I think your plan is too stupid.

    It's hard not to wonder if your server is going crazy with overselling.

    All you need to do is use more RAM, and more will be allocated. You are only using 1.2GB RAM, which is why you only have this much allocated by the balloon driver. The node you are on is already full, and no one has complained about performance. If you really want to see the 'total' RAM all the time, you can simply unload the balloon driver.

    Use the server however you intend and you'll see performance is exceptional in all aspects (which you can already see from all of the YABS that have been posted).

    Not really, you guys are severely compressing performance, I was able to use up to 4g-6g RAM before, and the CPU wouldn't even go to 100%. But now it's down to 2g RAM,CPU is consistently 100% and stability is terrible. My node-exporter can't even capture the data. docker app actually quits automatically.


    This has nothing to do with your the balloon driver?

    The CPU usage shouldn't have anything to do with balloon driver. Send a ticket and we will look into your issue, however you are also free to simply unload the balloon driver.

    Yabs benchmarking is really quality, but really after using this virtio_balloon module docker service is very unstable.
    After I disabled the module, docker went back to normal.

    Basic System Information:
---------------------------------
Uptime     : 0 days, 0 hours, 7 minutes
Processor  : AMD EPYC 7713 64-Core Processor
CPU cores  : 8 @ 1999.998 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM        : 15.6 GiB
Swap       : 0.0 KiB
Disk       : 77.6 GiB
Distro     : Debian GNU/Linux 11 (bullseye)
Kernel     : 5.10.0-25-amd64
VM Type    : KVM
IPv4/IPv6  : ✔ Online / ✔ Online

IPv6 Network Information:
---------------------------------
ISP        : DataWagon LLC
ASN        : AS27176 DataWagon LLC
Host       : DataWagon LLC
Location   : New York, New York (NY)
Country    : United States

fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 318.87 MB/s  (79.7k) | 4.10 GB/s    (64.0k)
Write      | 319.71 MB/s  (79.9k) | 4.12 GB/s    (64.4k)
Total      | 638.59 MB/s (159.6k) | 8.22 GB/s   (128.5k)
           |                      |                     
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 9.77 GB/s    (19.0k) | 2.31 GB/s     (2.2k)
Write      | 10.29 GB/s   (20.1k) | 2.46 GB/s     (2.4k)
Total      | 20.06 GB/s   (39.1k) | 4.77 GB/s     (4.6k)

iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 50.9 Mbits/sec  | 68.1 Mbits/sec  | 140 ms         
Scaleway        | Paris, FR (10G)           | busy            | busy            | 87.6 ms        
NovoServe       | North Holland, NL (40G)   | busy            | busy            | 146 ms         
Uztelecom       | Tashkent, UZ (10G)        | 301 Mbits/sec   | 296 Mbits/sec   | 230 ms         
Clouvider       | NYC, NY, US (10G)         | 394 Mbits/sec   | 812 Mbits/sec   | 74.6 ms        
Clouvider       | Dallas, TX, US (10G)      | 121 Mbits/sec   | 198 Mbits/sec   | 113 ms         
Clouvider       | Los Angeles, CA, US (10G) | 62.5 Mbits/sec  | 139 Mbits/sec   | 136 ms         

iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 21.1 Mbits/sec  | 33.7 Mbits/sec  | 140 ms         
Scaleway        | Paris, FR (10G)           | busy            | 281 Mbits/sec   | 154 ms         
NovoServe       | North Holland, NL (40G)   | busy            | busy            | 146 ms         
Uztelecom       | Tashkent, UZ (10G)        | 113 Mbits/sec   | 185 Mbits/sec   | 230 ms         
Clouvider       | NYC, NY, US (10G)         | 44.6 Mbits/sec  | 66.2 Mbits/sec  | 74.5 ms        
Clouvider       | Dallas, TX, US (10G)      | 24.7 Mbits/sec  | 64.0 Mbits/sec  | 113 ms         
Clouvider       | Los Angeles, CA, US (10G) | 16.0 Mbits/sec  | 45.7 Mbits/sec  | 136 ms         

Geekbench 6 Benchmark Test:
---------------------------------
Test            | Value                         
                |                               
Single Core     | 1416                          
Multi Core      | 7217                          
Full Test       | https://browser.geekbench.com/v6/cpu/2671525

    How did you disable virtio_balloon module?

  • DataWagonDataWagon Member, Patron Provider

    @nvme said:

    @sayyiku said:

    @DataWagon said:

    @sayyiku said:

    @DataWagon said:

    @sayyiku said:

    I think your plan is too stupid.

    It's hard not to wonder if your server is going crazy with overselling.

    All you need to do is use more RAM, and more will be allocated. You are only using 1.2GB RAM, which is why you only have this much allocated by the balloon driver. The node you are on is already full, and no one has complained about performance. If you really want to see the 'total' RAM all the time, you can simply unload the balloon driver.

    Use the server however you intend and you'll see performance is exceptional in all aspects (which you can already see from all of the YABS that have been posted).

    Not really, you guys are severely compressing performance, I was able to use up to 4g-6g RAM before, and the CPU wouldn't even go to 100%. But now it's down to 2g RAM,CPU is consistently 100% and stability is terrible. My node-exporter can't even capture the data. docker app actually quits automatically.


    This has nothing to do with your the balloon driver?

    The CPU usage shouldn't have anything to do with balloon driver. Send a ticket and we will look into your issue, however you are also free to simply unload the balloon driver.

    Yabs benchmarking is really quality, but really after using this virtio_balloon module docker service is very unstable.
    After I disabled the module, docker went back to normal.

    Basic System Information:
---------------------------------
Uptime     : 0 days, 0 hours, 7 minutes
Processor  : AMD EPYC 7713 64-Core Processor
CPU cores  : 8 @ 1999.998 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM        : 15.6 GiB
Swap       : 0.0 KiB
Disk       : 77.6 GiB
Distro     : Debian GNU/Linux 11 (bullseye)
Kernel     : 5.10.0-25-amd64
VM Type    : KVM
IPv4/IPv6  : ✔ Online / ✔ Online

IPv6 Network Information:
---------------------------------
ISP        : DataWagon LLC
ASN        : AS27176 DataWagon LLC
Host       : DataWagon LLC
Location   : New York, New York (NY)
Country    : United States

fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 318.87 MB/s  (79.7k) | 4.10 GB/s    (64.0k)
Write      | 319.71 MB/s  (79.9k) | 4.12 GB/s    (64.4k)
Total      | 638.59 MB/s (159.6k) | 8.22 GB/s   (128.5k)
           |                      |                     
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 9.77 GB/s    (19.0k) | 2.31 GB/s     (2.2k)
Write      | 10.29 GB/s   (20.1k) | 2.46 GB/s     (2.4k)
Total      | 20.06 GB/s   (39.1k) | 4.77 GB/s     (4.6k)

iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 50.9 Mbits/sec  | 68.1 Mbits/sec  | 140 ms         
Scaleway        | Paris, FR (10G)           | busy            | busy            | 87.6 ms        
NovoServe       | North Holland, NL (40G)   | busy            | busy            | 146 ms         
Uztelecom       | Tashkent, UZ (10G)        | 301 Mbits/sec   | 296 Mbits/sec   | 230 ms         
Clouvider       | NYC, NY, US (10G)         | 394 Mbits/sec   | 812 Mbits/sec   | 74.6 ms        
Clouvider       | Dallas, TX, US (10G)      | 121 Mbits/sec   | 198 Mbits/sec   | 113 ms         
Clouvider       | Los Angeles, CA, US (10G) | 62.5 Mbits/sec  | 139 Mbits/sec   | 136 ms         

iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 21.1 Mbits/sec  | 33.7 Mbits/sec  | 140 ms         
Scaleway        | Paris, FR (10G)           | busy            | 281 Mbits/sec   | 154 ms         
NovoServe       | North Holland, NL (40G)   | busy            | busy            | 146 ms         
Uztelecom       | Tashkent, UZ (10G)        | 113 Mbits/sec   | 185 Mbits/sec   | 230 ms         
Clouvider       | NYC, NY, US (10G)         | 44.6 Mbits/sec  | 66.2 Mbits/sec  | 74.5 ms        
Clouvider       | Dallas, TX, US (10G)      | 24.7 Mbits/sec  | 64.0 Mbits/sec  | 113 ms         
Clouvider       | Los Angeles, CA, US (10G) | 16.0 Mbits/sec  | 45.7 Mbits/sec  | 136 ms         

Geekbench 6 Benchmark Test:
---------------------------------
Test            | Value                         
                |                               
Single Core     | 1416                          
Multi Core      | 7217                          
Full Test       | https://browser.geekbench.com/v6/cpu/2671525

    How did you disable virtio_balloon module?

    Run 'rmmod virtio_balloon'. We are working on some configuration changes to make ballooning less prevalent. It's ballooning way more than it should at the moment.

    Thanked by 1khalequzzaman
  • nvmenvme Member

    @DataWagon said:

    @nvme said:

    @sayyiku said:

    @DataWagon said:

    @sayyiku said:

    @DataWagon said:

    @sayyiku said:

    I think your plan is too stupid.

    It's hard not to wonder if your server is going crazy with overselling.

    All you need to do is use more RAM, and more will be allocated. You are only using 1.2GB RAM, which is why you only have this much allocated by the balloon driver. The node you are on is already full, and no one has complained about performance. If you really want to see the 'total' RAM all the time, you can simply unload the balloon driver.

    Use the server however you intend and you'll see performance is exceptional in all aspects (which you can already see from all of the YABS that have been posted).

    Not really, you guys are severely compressing performance, I was able to use up to 4g-6g RAM before, and the CPU wouldn't even go to 100%. But now it's down to 2g RAM,CPU is consistently 100% and stability is terrible. My node-exporter can't even capture the data. docker app actually quits automatically.


    This has nothing to do with your the balloon driver?

    The CPU usage shouldn't have anything to do with balloon driver. Send a ticket and we will look into your issue, however you are also free to simply unload the balloon driver.

    Yabs benchmarking is really quality, but really after using this virtio_balloon module docker service is very unstable.
    After I disabled the module, docker went back to normal.

    Basic System Information:
---------------------------------
Uptime     : 0 days, 0 hours, 7 minutes
Processor  : AMD EPYC 7713 64-Core Processor
CPU cores  : 8 @ 1999.998 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM        : 15.6 GiB
Swap       : 0.0 KiB
Disk       : 77.6 GiB
Distro     : Debian GNU/Linux 11 (bullseye)
Kernel     : 5.10.0-25-amd64
VM Type    : KVM
IPv4/IPv6  : ✔ Online / ✔ Online

IPv6 Network Information:
---------------------------------
ISP        : DataWagon LLC
ASN        : AS27176 DataWagon LLC
Host       : DataWagon LLC
Location   : New York, New York (NY)
Country    : United States

fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 318.87 MB/s  (79.7k) | 4.10 GB/s    (64.0k)
Write      | 319.71 MB/s  (79.9k) | 4.12 GB/s    (64.4k)
Total      | 638.59 MB/s (159.6k) | 8.22 GB/s   (128.5k)
           |                      |                     
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ---- 
Read       | 9.77 GB/s    (19.0k) | 2.31 GB/s     (2.2k)
Write      | 10.29 GB/s   (20.1k) | 2.46 GB/s     (2.4k)
Total      | 20.06 GB/s   (39.1k) | 4.77 GB/s     (4.6k)

iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 50.9 Mbits/sec  | 68.1 Mbits/sec  | 140 ms         
Scaleway        | Paris, FR (10G)           | busy            | busy            | 87.6 ms        
NovoServe       | North Holland, NL (40G)   | busy            | busy            | 146 ms         
Uztelecom       | Tashkent, UZ (10G)        | 301 Mbits/sec   | 296 Mbits/sec   | 230 ms         
Clouvider       | NYC, NY, US (10G)         | 394 Mbits/sec   | 812 Mbits/sec   | 74.6 ms        
Clouvider       | Dallas, TX, US (10G)      | 121 Mbits/sec   | 198 Mbits/sec   | 113 ms         
Clouvider       | Los Angeles, CA, US (10G) | 62.5 Mbits/sec  | 139 Mbits/sec   | 136 ms         

iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
-----           | -----                     | ----            | ----            | ----           
Clouvider       | London, UK (10G)          | 21.1 Mbits/sec  | 33.7 Mbits/sec  | 140 ms         
Scaleway        | Paris, FR (10G)           | busy            | 281 Mbits/sec   | 154 ms         
NovoServe       | North Holland, NL (40G)   | busy            | busy            | 146 ms         
Uztelecom       | Tashkent, UZ (10G)        | 113 Mbits/sec   | 185 Mbits/sec   | 230 ms         
Clouvider       | NYC, NY, US (10G)         | 44.6 Mbits/sec  | 66.2 Mbits/sec  | 74.5 ms        
Clouvider       | Dallas, TX, US (10G)      | 24.7 Mbits/sec  | 64.0 Mbits/sec  | 113 ms         
Clouvider       | Los Angeles, CA, US (10G) | 16.0 Mbits/sec  | 45.7 Mbits/sec  | 136 ms         

Geekbench 6 Benchmark Test:
---------------------------------
Test            | Value                         
                |                               
Single Core     | 1416                          
Multi Core      | 7217                          
Full Test       | https://browser.geekbench.com/v6/cpu/2671525

    How did you disable virtio_balloon module?

    Run 'rmmod virtio_balloon'. We are working on some configuration changes to make ballooning less prevalent. It's ballooning way more than it should at the moment.

    I did tried that, but it says it is built in, so unable to disable it. I am using ubuntu 20 image.
    I don't have problem with ballooning, but it is abusing swap rather than using memory so wanted to give it a try

  • ipguruipguru Member

    @DataWagon said:
    Chicago is coming next, LA is probably a few months out, but we hope to add it soon.

    Timeline or pre-order links?

  • spikezzspikezz Member

    Very good servers, but the support is almost inexistent.
    The fastest that they ansewered was within 12 hours and I got a ticket opened 2 days ago (#912990) asking how much would it be to increase the disk space and I haven't heard back from them yet.

    I imagine if I really need their support someday...

  • DataWagonDataWagon Member, Patron Provider
    edited September 23

    @spikezz said:
    Very good servers, but the support is almost inexistent.
    The fastest that they ansewered was within 12 hours and I got a ticket opened 2 days ago (#912990) asking how much would it be to increase the disk space and I haven't heard back from them yet.

    I imagine if I really need their support someday...

    Sales requests are not the same as support. Sales / custom spec inquiries are handled at a lower priority than support requests. We have 24/7 staff to handle support issues.

  • seventhsky42seventhsky42 Member

    We bought VPS and all are running on more than 98% RAM.
    https://prnt.sc/e9c3IFUtkEjc - #765134

  • ipguruipguru Member
    edited September 24

    @seventhsky42 said:
    We bought VPS and all are running on more than 98% RAM.
    https://prnt.sc/e9c3IFUtkEjc - #765134

    Oops, not enough coffee, my earlier comment was for Linux.

  • dev_vpsdev_vps Member

    @seventhsky42 said:
    We bought VPS and all are running on more than 98% RAM.
    https://prnt.sc/e9c3IFUtkEjc - #765134

    it is better if for Windows OS based VPS,
    RAM and Disk Space is dedicated and not shared

    shared cpu cores is fine.

  • dev_vpsdev_vps Member
    edited September 24

    @seventhsky42 said:
    We bought VPS and all are running on more than 98% RAM.
    https://prnt.sc/e9c3IFUtkEjc - #765134

    @DataWagon @seventhsky42
    This is how memory utilization should look without balloon effect

  • DataWagonDataWagon Member, Patron Provider

    @dev_vps @seventhsky42 @nvme @sayyiku @swag @shizuosec

    We made some configuration changes on the node today that should fix this. Ballooning has been disabled and some other tweaks have been made. Check now and see if it's working as expected.

    Thanked by 3amaeva080 nvme swag
  • aryaandasaryaandas Member

    Looks promising, Will probably get few

  • stryker09stryker09 Member

    @DataWagon said:
    @dev_vps @seventhsky42 @nvme @sayyiku @swag @shizuosec

    We made some configuration changes on the node today that should fix this. Ballooning has been disabled and some other tweaks have been made. Check now and see if it's working as expected.

    Looks to have improved on my end

  • houmiehoumie Member

    @febryanvaldo said:

    @sayyiku said: Any Yabs ?
    @jingfanqin said: yabs?

    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
#              Yet-Another-Bench-Script              #
#                     v2023-09-06                    #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #

    > Wed Sep 13 03:25:03 AM UTC 2023
> 
> Basic System Information:
> ---------------------------------
> Uptime     : 0 days, 0 hours, 7 minutes
> Processor  : AMD EPYC 7713 64-Core Processor
> CPU cores  : 4 @ 1999.998 MHz
> AES-NI     : ✔ Enabled
> VM-x/AMD-V : ✔ Enabled
> RAM        : 7.8 GiB
> Swap       : 1022.0 MiB
> Disk       : 38.3 GiB
> Distro     : Ubuntu 22.04.3 LTS
> Kernel     : 5.15.0-83-generic
> VM Type    : KVM
> IPv4/IPv6  : ✔ Online / ✔ Online
> 
> IPv6 Network Information:
> ---------------------------------
> ISP        : DataWagon LLC
> ASN        : AS27176 DataWagon LLC
> Host       : DataWagon LLC
> Location   : New York, New York (NY)
> Country    : United States
> 
> fio Disk Speed Tests (Mixed R/W 50/50):
> ---------------------------------
> Block Size | 4k            (IOPS) | 64k           (IOPS)
>   ------   | ---            ----  | ----           ----
> Read       | 409.14 MB/s (102.2k) | 3.82 GB/s    (59.7k)
> Write      | 410.21 MB/s (102.5k) | 3.84 GB/s    (60.0k)
> Total      | 819.35 MB/s (204.8k) | 7.66 GB/s   (119.8k)
>            |                      |
> Block Size | 512k          (IOPS) | 1m            (IOPS)
>   ------   | ---            ----  | ----           ----
> Read       | 4.07 GB/s     (7.9k) | 4.82 GB/s     (4.7k)
> Write      | 4.29 GB/s     (8.3k) | 5.14 GB/s     (5.0k)
> Total      | 8.37 GB/s    (16.3k) | 9.96 GB/s     (9.7k)
> 
> Geekbench 5 Benchmark Test:
> ---------------------------------
> Test            | Value
>                 |
> Single Core     | 1122
> Multi Core      | 4305
> Full Test       | https://browser.geekbench.com/v5/cpu/21700533
> 
> Geekbench 6 Benchmark Test:
> ---------------------------------
> Test            | Value
>                 |
> Single Core     | 1436
> Multi Core      | 4693
> Full Test       | https://browser.geekbench.com/v6/cpu/2584982
>

    Hi, The YABS isn't complete. The most important part is the IPv4 speed, which is important to me. Any chance you could publish the full YABS, please? Thanks

  • febryanvaldofebryanvaldo Member

    @houmie said: Hi, The YABS isn't complete. The most important part is the IPv4 speed, which is important to me. Any chance you could publish the full YABS, please? Thanks

    Just hit my signature. I have benchmarked this VPS.

    Thanked by 1Fireboy
  • ourvdsourvds Member
    edited September 28

    Del

  • seventhsky42seventhsky42 Member

    Invoice #21194 - Still pending, thought it was automatic.

Sign In or Register to comment.