/ Register

Want more timely Centmin Mod News Updates?
Become a Member

VULTR - Launches Bare Betal

Discussion in 'Dedicated server hosting' started by ArisC, Dec 2, 2017.

Previous Thread Next Thread
Loading...
  1. Dec 2, 2017 #1
    ArisC

    ArisC Active Member

    113
    27
    28
    Jun 1, 2017
    Ratings:
    +52
    Local Time:
    9:59 PM
    Nginx Latest
    MariaDB Latest
    From the beginning, the team at Vultr has focused on making all aspects of hosting infrastructure management easier for everyone. Today we are excited to bring the simplicity of the Vultr platform to an old hosting industry stalwart - dedicated servers - by introducing the brand new Vultr Bare Metal product line!

    Powered by Vultr's cloud orchestration, you can now easily deploy single-tenant physical dedicated servers with zero virtualization layer. We’ve also added an array of cloud features typically only available for standard compute, such as hourly billing, fast api-driven deployment, and availability in multiple geographic regions.

    Direct Hardware Access
    Vultr Bare Metal provides direct access to the full power of the underlying physical hardware without a virtualization layer. On our platform, you'll be in the driver's seat of a real, physical server, with the convenience and simplicity of Vultr automation. Bare metal servers are also single-tenant only which means that only you will have full access to the resources of your server.

    Worldwide Deployment
    Deploy bare metal hardware around the world in 10 minutes or less using our point-and-click control panel. We are first introducing bare metal in Singapore and more locations will be rolled out in the coming weeks.

    Flexible Resource Management
    Easily scale and customize your bare metal environment via our user-friendly customer portal or by using our flexible API. In addition, all bare metal plans include the same no long term contract terms and hourly billing you’ve come to expect from our standard compute offerings.

    All Standard Operating Systems
    The complete Vultr operating system library has been updated to support bare metal servers. This includes all our versions of Linux, Windows, and BSD with full root/administrator access. Seamlessly switch between virtual and bare metal hardware without having to compromise!

    Bare metal adds the proven performance and security of the Vultr platform. Read more about bare metal servers on our product page and deploy a bare metal server today!


    Read more here
     
    • Informative Informative x 2
  2. Dec 2, 2017 #2
    eva2000

    eva2000 Administrator Staff Member

    36,059
    7,912
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +12,194
    Local Time:
    4:59 AM
    Nginx 1.15.x
    MariaDB 5.5/10.x
    Wow didn't expect to hear this news. Amazon AWS EC2 has similar announcement here. Bare metal seems to be in these days so going full circle from dedicated bare metal, to vps, to cloud and now back to bare metal and hybrid mixed cloud/bare metal environments :)

    Interesting choice to start with roll out in Singapore of all places ! Would of though New Jersey/New York would be first up on deployed releases.
     
    • Agree Agree x 1
  3. Dec 2, 2017 #3
    Igor

    Igor New Member

    4
    2
    3
    Nov 28, 2017
    Ratings:
    +4
    Local Time:
    8:59 PM
    1.13.7
    10.2
    $300 per month is a lot but the hourly billing is what makes this really interesting. Rent it for a day, do your stuff and shut it down. Good biz decision from Vultr if you ask me.
     
    • Agree Agree x 1
  4. Dec 2, 2017 #4
    ArisC

    ArisC Active Member

    113
    27
    28
    Jun 1, 2017
    Ratings:
    +52
    Local Time:
    9:59 PM
    Nginx Latest
    MariaDB Latest
    They will add Atom Processors.... So it will probably be cheaper
     
  5. Dec 3, 2017 #5
    Igor

    Igor New Member

    4
    2
    3
    Nov 28, 2017
    Ratings:
    +4
    Local Time:
    8:59 PM
    1.13.7
    10.2
    I'll wait for their pricing on them but having in mind something like Scaleway, they are going to have to work hard on their pricing. I think Scaleway is running Atom Avoton's on some of their bare metal machines packages.
     
  6. Dec 3, 2017 #6
    pamamolf

    pamamolf Well-Known Member

    3,113
    295
    83
    May 31, 2014
    Ratings:
    +530
    Local Time:
    9:59 PM
    Nginx-1.13.x
    MariaDB 10.1.x
    Very expensive!!!
     
  7. Dec 4, 2017 #7
    rdan

    rdan Premium Member Premium Member

    4,256
    1,035
    113
    May 25, 2014
    Ratings:
    +1,487
    Local Time:
    2:59 AM
    Mainline
    10.2
    x2 with my OVH Singapore (OVH having higher specs) :D.
     
  8. Dec 4, 2017 #8
    rdan

    rdan Premium Member Premium Member

    4,256
    1,035
    113
    May 25, 2014
    Ratings:
    +1,487
    Local Time:
    2:59 AM
    Mainline
    10.2
    VULTR No Raid Setup and Mounted.
     
    • Informative Informative x 3
  9. Dec 4, 2017 #9
    rdan

    rdan Premium Member Premium Member

    4,256
    1,035
    113
    May 25, 2014
    Ratings:
    +1,487
    Local Time:
    2:59 AM
    Mainline
    10.2
    centminmodbench.sh Result:
    Code:
    -------------------------------------------
centminmodbench.sh 0.9.5
http://bench.centminmod.com
written by: George Liu (eva2000)
http://centminmod.com
-------------------------------------------

-------------------------------------------
System Information
-------------------------------------------

3.10.0-693.5.2.el7.x86_64

CentOS Linux release 7.4.1708 (Core) 

Centmin Mod 
----------------------------------------------
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                8
On-line CPU(s) list:   0-7
Thread(s) per core:    2
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 158
Model name:            Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz
Stepping:              9
CPU MHz:               4099.695
CPU max MHz:           4200.0000
CPU min MHz:           800.0000
BogoMIPS:              7584.00
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              8192K
NUMA node0 CPU(s):     0-7
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp

CPU Flags
 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp

----------------------------------------------
CPU NODE SOCKET CORE L1d:L1i:L2:L3 ONLINE MAXMHZ    MINMHZ
0   0    0      0    0:0:0:0       yes    4200.0000 800.0000
1   0    0      1    1:1:1:0       yes    4200.0000 800.0000
2   0    0      2    2:2:2:0       yes    4200.0000 800.0000
3   0    0      3    3:3:3:0       yes    4200.0000 800.0000
4   0    0      0    0:0:0:0       yes    4200.0000 800.0000
5   0    0      1    1:1:1:0       yes    4200.0000 800.0000
6   0    0      2    2:2:2:0       yes    4200.0000 800.0000
7   0    0      3    3:3:3:0       yes    4200.0000 800.0000

----------------------------------------------
              total        used        free      shared  buff/cache   available
Mem:          31837        1353       30148          22         335       30112
Low:          31837        1688       30148
High:             0           0           0
Swap:          1023           0        1023

----------------------------------------------
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       221G  6.5G  203G   4% /
devtmpfs         16G  4.0K   16G   1% /dev
tmpfs            16G     0   16G   0% /dev/shm
tmpfs            16G  8.6M   16G   1% /run
tmpfs            16G     0   16G   0% /sys/fs/cgroup
/dev/sdb1       220G   61M  209G   1% /data
tmpfs           3.2G     0  3.2G   0% /run/user/0
tmpfs            16G   24K   16G   1% /tmp
    Code:
    -------------------------------------------
disk ioping tests
-------------------------------------------

2017-12-03 21:57:48 URL:https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/ioping/ioping-0.8.tar.gz [10590/10590] -> "ioping-0.8.tar.gz" [1]
Download done.
ioping-0.8.tar.gz valid file.

Running IOPing I/O benchmark...
cc -std=gnu99 -g -Wall -Wextra -pedantic -DVERSION=\"0.8\" -c -o ioping.o ioping.c
cc -o ioping ioping.o -std=gnu99 -g -Wall -Wextra -pedantic  -lm

IOPing I/O: ./ioping -c 10 .
4.0 KiB from . (ext4 /dev/sda1): request=1 time=474 us
4.0 KiB from . (ext4 /dev/sda1): request=2 time=240 us
4.0 KiB from . (ext4 /dev/sda1): request=3 time=240 us
4.0 KiB from . (ext4 /dev/sda1): request=4 time=222 us
4.0 KiB from . (ext4 /dev/sda1): request=5 time=376 us
4.0 KiB from . (ext4 /dev/sda1): request=6 time=232 us
4.0 KiB from . (ext4 /dev/sda1): request=7 time=205 us
4.0 KiB from . (ext4 /dev/sda1): request=8 time=240 us
4.0 KiB from . (ext4 /dev/sda1): request=9 time=230 us
4.0 KiB from . (ext4 /dev/sda1): request=10 time=236 us

--- . (ext4 /dev/sda1) ioping statistics ---
10 requests completed in 9.0 s, 3.7 k iops, 14.5 MiB/s
min/avg/max/mdev = 205 us / 269 us / 474 us / 81 us

IOPing seek rate: ./ioping -RD .

--- . (ext4 /dev/sda1) ioping statistics ---
19.4 k requests completed in 3.0 s, 6.5 k iops, 25.3 MiB/s
min/avg/max/mdev = 117 us / 154 us / 1.2 ms / 31 us

IOPing sequential: ./ioping -RL .

--- . (ext4 /dev/sda1) ioping statistics ---
1.9 k requests completed in 3.0 s, 622 iops, 155.6 MiB/s
min/avg/max/mdev = 729 us / 1.6 ms / 3.4 ms / 351 us

IOPing cached: ./ioping -RC .

--- . (ext4 /dev/sda1) ioping statistics ---
6.3 M requests completed in 3.0 s, 2.3 M iops, 8.8 GiB/s
min/avg/max/mdev = 0 us / 0 us / 24 us / 0 us
    Code:
    -------------------------------------------
disk DD tests
-------------------------------------------

dd if=/dev/zero of=sb-io-test bs=1M count=1k conv=fdatasync
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 3.55647 s, 302 MB/s

dd if=/dev/zero of=sb-io-test bs=64k count=16k conv=fdatasync
16384+0 records in
16384+0 records out
1073741824 bytes (1.1 GB) copied, 3.53975 s, 303 MB/s

dd if=/dev/zero of=sb-io-test bs=1M count=1k oflag=dsync
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 3.70432 s, 290 MB/s

dd if=/dev/zero of=sb-io-test bs=64k count=16k oflag=dsync
16384+0 records in
16384+0 records out
1073741824 bytes (1.1 GB) copied, 9.80835 s, 109 MB/s
    Code:
    -------------------------------------------
disk FIO tests
-------------------------------------------

2017-12-03 21:58:31 URL:https://raw.githubusercontent.com/Crowd9/Benchmark/master/fio-2.0.9.tar.gz [275092/275092] -> "fio-2.0.9.tar.gz" [1]
Download done.
fio-2.0.9.tar.gz valid file.

Running FIO benchmark...

FIO_VERSION = fio-2.0.9
    DEP .depend
    CC gettime.o
    CC fio.o
    CC ioengines.o
    CC init.o
    CC stat.o
    CC log.o
    CC time.o
    CC filesetup.o
    CC eta.o
    CC verify.o
    CC memory.o
    CC io_u.o
    CC parse.o
    CC mutex.o
    CC options.o
    CC rbtree.o
    CC smalloc.o
    CC filehash.o
    CC profile.o
    CC debug.o
    CC lib/rand.o
    CC lib/num2str.o
    CC lib/ieee754.o
    CC crc/crc16.o
    CC crc/sha512.o
    CC crc/crc7.o
    CC crc/sha1.o
    CC crc/crc32c.o
    CC crc/crc32.o
    CC crc/crc32c-intel.o
    CC crc/sha256.o
    CC crc/md5.o
    CC crc/crc64.o
    CC engines/cpu.o
    CC engines/mmap.o
    CC engines/sync.o
    CC engines/null.o
    CC engines/net.o
    CC memalign.o
    CC server.o
    CC client.o
    CC iolog.o
    CC backend.o
    CC libfio.o
    CC flow.o
    CC diskutil.o
    CC fifo.o
    CC blktrace.o
    CC helpers.o
    CC cgroup.o
    CC trim.o
    CC engines/libaio.o
    CC engines/posixaio.o
    CC engines/sg.o
    CC engines/splice.o
    CC engines/syslet-rw.o
    CC engines/guasi.o
    CC engines/binject.o
    CC engines/rdma.o
    CC profiles/tiobench.o
    CC fio

FIO random reads: 
randomreads: (g=0): rw=randread, bs=4K-4K/4K-4K, ioengine=libaio, iodepth=64
fio-2.0.9
Starting 1 process
randomreads: Laying out IO file(s) (1 file(s) / 1024MB)

randomreads: (groupid=0, jobs=1): err= 0: pid=28456: Sun Dec  3 21:58:40 2017
  read : io=1024.3MB, bw=254138KB/s, iops=63534 , runt=  4127msec
  cpu          : usr=5.21%, sys=21.09%, ctx=245326, majf=0, minf=83
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%
     issued    : total=r=262207/w=0/d=0, short=r=0/w=0/d=0

Run status group 0 (all jobs):
   READ: io=1024.3MB, aggrb=254138KB/s, minb=254138KB/s, maxb=254138KB/s, mint=4127msec, maxt=4127msec

Disk stats (read/write):
  sda: ios=249688/0, merge=61/0, ticks=250038/0, in_queue=250033, util=97.54%

FIO random writes: 
randomwrites: (g=0): rw=randwrite, bs=4K-4K/4K-4K, ioengine=libaio, iodepth=64
fio-2.0.9
Starting 1 process

randomwrites: (groupid=0, jobs=1): err= 0: pid=28460: Sun Dec  3 21:58:47 2017
  write: io=1024.3MB, bw=167197KB/s, iops=41799 , runt=  6273msec
  cpu          : usr=4.21%, sys=14.70%, ctx=252342, majf=0, minf=18
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%
     issued    : total=r=0/w=262207/d=0, short=r=0/w=0/d=0

Run status group 0 (all jobs):
  WRITE: io=1024.3MB, aggrb=167197KB/s, minb=167197KB/s, maxb=167197KB/s, mint=6273msec, maxt=6273msec

Disk stats (read/write):
  sda: ios=0/257100, merge=0/68, ticks=0/393759, in_queue=393807, util=98.45%
    Code:
    -------------------------------------------
ramdisk DD tests - memory bandwidth
-------------------------------------------

dd if=/dev/zero of=sb-io-test bs=128k count=1k conv=fdatasync
1024+0 records in
1024+0 records out
134217728 bytes (134 MB) copied, 0.0267813 s, 5.0 GB/s

dd if=/dev/zero of=sb-io-test bs=8k count=16k conv=fdatasync
16384+0 records in
16384+0 records out
134217728 bytes (134 MB) copied, 0.0280197 s, 4.8 GB/s

dd if=/dev/zero of=sb-io-test bs=128k count=1k oflag=dsync
1024+0 records in
1024+0 records out
134217728 bytes (134 MB) copied, 0.0261215 s, 5.1 GB/s

dd if=/dev/zero of=sb-io-test bs=8k count=16k oflag=dsync
16384+0 records in
16384+0 records out
134217728 bytes (134 MB) copied, 0.028471 s, 4.7 GB/s
    Code:
    -------------------------------------------
ramdisk ioping tests - memory bandwidth
-------------------------------------------

2017-12-03 21:58:47 URL:https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/ioping/ioping-0.8.tar.gz [10590/10590] -> "ioping-0.8.tar.gz" [1]
Download done.
ioping-0.8.tar.gz valid file.

Running IOPing I/O ramdisk benchmark...
cc -std=gnu99 -g -Wall -Wextra -pedantic -DVERSION=\"0.8\" -c -o ioping.o ioping.c
cc -o ioping ioping.o -std=gnu99 -g -Wall -Wextra -pedantic  -lm

IOPing I/O: ./ioping -c 10 .
4.0 KiB from . (tmpfs tmpfs): request=1 time=1 us
4.0 KiB from . (tmpfs tmpfs): request=2 time=4 us
4.0 KiB from . (tmpfs tmpfs): request=3 time=3 us
4.0 KiB from . (tmpfs tmpfs): request=4 time=3 us
4.0 KiB from . (tmpfs tmpfs): request=5 time=3 us
4.0 KiB from . (tmpfs tmpfs): request=6 time=3 us
4.0 KiB from . (tmpfs tmpfs): request=7 time=3 us
4.0 KiB from . (tmpfs tmpfs): request=8 time=3 us
4.0 KiB from . (tmpfs tmpfs): request=9 time=3 us
4.0 KiB from . (tmpfs tmpfs): request=10 time=3 us

--- . (tmpfs tmpfs) ioping statistics ---
10 requests completed in 9.0 s, 344.8 k iops, 1.3 GiB/s
min/avg/max/mdev = 1 us / 2 us / 4 us / 0 us

IOPing seek rate: ./ioping -R .

--- . (tmpfs tmpfs) ioping statistics ---
3.0 M requests completed in 3.0 s, 2.4 M iops, 9.2 GiB/s
min/avg/max/mdev = 0 us / 0 us / 23 us / 0 us

IOPing sequential: ./ioping -RL .

--- . (tmpfs tmpfs) ioping statistics ---
88.2 k requests completed in 3.0 s, 47.4 k iops, 11.6 GiB/s
min/avg/max/mdev = 17 us / 21 us / 61 us / 1 us

IOPing cached: ./ioping -RC .

--- . (tmpfs tmpfs) ioping statistics ---
5.8 M requests completed in 3.0 s, 2.1 M iops, 8.1 GiB/s
min/avg/max/mdev = 0 us / 0 us / 52 us / 0 us
     
    • Informative Informative x 2
  10. Dec 5, 2017 #10
    Colin

    Colin Premium Member Premium Member

    138
    40
    28
    Oct 7, 2015
    Sheffield UK
    Ratings:
    +100
    Local Time:
    7:59 PM
    1.13.#
    MariaDB 10.1.#
    I was reading the other day how packet.net can't wait for aws to validate their 'bare' proposal.
    Why We Can’t Wait for AWS to Announce Bare Metal

    I've not tested packet; but quite tempted to, as the 'scaling' up is too extreme. A type0 to type 1 step in monthly is huge! Admittedly you also get huge bump in hardware. If the type0 had 2 ssd then I'd go for it tbh. Darn near perfect container host.

    So I set to finding an alternative, Scaleway is one. Also pushing arm baremetal, 4cores 2gb/50gb disk for <3 euro a month... None are as straightforward as a vps of the linode/do/vultr stack, but then it's a little more complex to get baremetal + attached disk I guess. I was looking to attach volumes to make raid, tbh I think I'd run a few more given the cost and anything volatile ship out to amazon/block storage. Why make life too difficult ;)

    Will be keen to see vultrs pricing. TBH I didn't think $300 was too bad. It's less than packet for example. It's more than vps, but not much more. I still have a $200 dollar linode that gets noisy neighbours. by rights I should of moved it off ages ago... but I'll pay a bit more for convenience.

    I'm actually tempted once they breakout of singapore.
     
Previous Thread Next Thread
Loading...
..

.