OVH New SP-32 and SP-64 2017 with E3-1270v6 4c/8th 3.8/4.2GHz and vRack!

Harambe · April 2017

@FredQc said:

This is not what I see.

This is what I'm looking at right now: http://i.imgur.com/iVjpfFx.png

FredQc · April 2017

@Harambe said:

@FredQc said:

This is not what I see.

This is what I'm looking at right now: http://i.imgur.com/iVjpfFx.png

Yeah, I had to empty my cache. Still a little bit cheaper on the CA site when doing currency conversion, thought.

deadbeef · April 2017

@Falzo said:

@deadbeef said:
@Falzo You are confused and just spouting nonsense.

yeah maybe, if that's what's working for you ;-)

You got that right, the law is what's working for me. Maybe you should try that.

on the other hand I am not talking about selling goods here, but selling services which again is something different in terms of tax laws.

Didn't you go to school? Reading is too difficult a process for you? I pasted two screenshots- one for goods and one for services. Both say the same thing - no VAT. Both state it in bold. How hard is it to get?

pbgben · April 2017

@LaDc said:

@Harambe said:

@pbgben said:
We've already got NVMe in our BHS location. Soo fast ;P

What, no promo? Hit us with a deal.

I second that

Okay, lets do something. Also have an nvme backed i7 7700 waiting for IP's to go live.

deadbeef · April 2017

@pbgben said:

@LaDc said:

@Harambe said:

@pbgben said:
We've already got NVMe in our BHS location. Soo fast ;P

What, no promo? Hit us with a deal.

I second that

Okay, lets do something. Also have an nvme backed i7 7700 waiting for IP's to go live.

No need to wait, launch a pre-launch super deal.

SprkFade · April 2017

@FredQc said:

@Harambe said:

@FredQc said:

SprkFade said: How much was your server? I ordered the same SP-32 but was charged $111.99 instead of the $86.99 that it should be with the 450 GB NVMe disks.

Where you see $86.99? SP-32 2017 w/ NVMe is $111.99/mo USD

US site shows $74.99 (new SP-32) + $12 for NVMe drives = $86.99. New SP-64 with NVMe drives is $116.99 USD.

This is not what I see.

Edit: OK, emptied the cache and it's showing the new price.

Seems like the site had the wrong pricing. Support confirmed and they're getting it fixed for me.

pbgben · April 2017

@deadbeef said:

@pbgben said:

@LaDc said:

@Harambe said:

@pbgben said:
We've already got NVMe in our BHS location. Soo fast ;P

What, no promo? Hit us with a deal.

I second that

Okay, lets do something. Also have an nvme backed i7 7700 waiting for IP's to go live.

No need to wait, launch a pre-launch super deal.

I really hoped I could get this going for easter, but OVH are who they are.

20% reccuring for the BHS node with NVMe if you want that instead.

https://billing.c38.host/cart.php?gid=3 CODE: EasterCunts

Harambe · April 2017

@pbgben said:

I really hoped I could get this going for easter, but OVH are who they are.

20% reccuring for the BHS node with NVMe if you want that instead.

https://billing.c38.host/cart.php?gid=3 CODE: EasterCunts

What's the performance looking like on those NVMe's?

pbgben · April 2017

@Harambe said:

@pbgben said:

I really hoped I could get this going for easter, but OVH are who they are.

20% reccuring for the BHS node with NVMe if you want that instead.

https://billing.c38.host/cart.php?gid=3 CODE: EasterCunts

What's the performance looking like on those NVMe's?

BHS is fast, but the new i7 range is faster.

dd if=/dev/zero of=/tmp/output bs=8k count=10k; rm -f /tmp/I know, but it looks better!

10240+0 records in
10240+0 records out
83886080 bytes (84 MB, 80 MiB) copied, 0.0357949 s, 2.3 GB/s

willie · April 2017

Do you have a random iops bench? That's what the NVMe is most interesting at.

rincewind · April 2017

pbgben said: Which model NVMe SSD did you get?

I have centos installed and can't get any cmd to tell me about them. Its the 450GB Option.

If the NVMe SSDs are on the PCI bus, they should show up in lspci -v. update-pciids to refresh PCI signatures if the drive shows up as unrecognized.

hdparm -I /dev/sda should also give the model number. There's also lshw and hwinfo to probe hardware.

pbgben · April 2017

@willie said:
Do you have a random iops bench? That's what the NVMe is most interesting at.

benchmark: (g=0): rw=randread, bs=4K-4K/4K-4K/4K-4K, ioengine=sync, iodepth=32
...
fio-2.8
Starting 8 processes
benchmark: Laying out IO file(s) (1 file(s) / 256MB)
benchmark: Laying out IO file(s) (1 file(s) / 256MB)
benchmark: Laying out IO file(s) (1 file(s) / 256MB)
benchmark: Laying out IO file(s) (1 file(s) / 256MB)
benchmark: Laying out IO file(s) (1 file(s) / 256MB)
benchmark: Laying out IO file(s) (1 file(s) / 256MB)
benchmark: Laying out IO file(s) (1 file(s) / 256MB)
benchmark: Laying out IO file(s) (1 file(s) / 256MB)

benchmark: (groupid=0, jobs=8): err= 0: pid=7787: Sun Apr 16 11:28:09 2017
  read : io=1134.1GB, bw=19370MB/s, iops=4958.7K, runt= 60001msec
    clat (usec): min=0, max=20018, avg= 1.14, stdev= 5.29
     lat (usec): min=0, max=20018, avg= 1.17, stdev= 5.29
    clat percentiles (usec):
     |  1.00th=[    0],  5.00th=[    0], 10.00th=[    0], 20.00th=[    1],
     | 30.00th=[    1], 40.00th=[    1], 50.00th=[    1], 60.00th=[    1],
     | 70.00th=[    1], 80.00th=[    1], 90.00th=[    1], 95.00th=[    2],
     | 99.00th=[    2], 99.50th=[    2], 99.90th=[   92], 99.95th=[  127],
     | 99.99th=[  171]
    bw (MB  /s): min=   29, max= 4448, per=12.49%, avg=2418.74, stdev=872.84
    lat (usec) : 2=94.03%, 4=5.78%, 10=0.02%, 20=0.01%, 50=0.01%
    lat (usec) : 100=0.09%, 250=0.08%, 500=0.01%, 750=0.01%, 1000=0.01%
    lat (msec) : 2=0.01%, 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%
  cpu          : usr=31.53%, sys=57.10%, ctx=569981, majf=0, minf=86
  IO depths    : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.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.0%, >=64=0.0%
     issued    : total=r=297526973/w=0/d=0, short=r=0/w=0/d=0, drop=r=0/w=0/d=0
     latency   : target=0, window=0, percentile=100.00%, depth=32

Run status group 0 (all jobs):
   READ: io=1134.1GB, aggrb=19370MB/s, minb=19370MB/s, maxb=19370MB/s, mint=60001msec, maxt=60001msec

Disk stats (read/write):
    md2: ios=524288/968, merge=0/0, ticks=0/0, in_queue=0, util=0.00%, aggrios=262144/495, aggrmerge=0/0, aggrticks=27158/8, aggrin_queue=27154, aggrutil=12.90%
  nvme0n1: ios=262144/529, merge=0/0, ticks=25648/8, in_queue=25644, util=12.79%
  nvme1n1: ios=262144/461, merge=0/0, ticks=28668/8, in_queue=28664, util=12.90%

jazz1611 · April 2017

can you tell me model nvme? ovh was remove the model nvme on home page

pbgben · April 2017

@rincewind said:

pbgben said: Which model NVMe SSD did you get?

I have centos installed and can't get any cmd to tell me about them. Its the 450GB Option.

If the NVMe SSDs are on the PCI bus, they should show up in lspci -v. update-pciids to refresh PCI signatures if the drive shows up as unrecognized.

hdparm -I /dev/sda should also give the model number. There's also lshw and hwinfo to probe hardware.
@willie said:
Do you have a random iops bench? That's what the NVMe is most interesting at.

https://serverscope.io/trials/YaM7

pbgben · April 2017

@jazz1611 said:
can you tell me model nvme? ovh was remove the model nvme on home page

Can't figure out how to tell on ubuntu

02:00.0 Non-Volatile memory controller: Intel Corporation Device 0a53 (rev 02) (prog-if 02 [NVM Express])
Subsystem: Intel Corporation Device 3705

jazz1611 · April 2017

@pbgben said:

@jazz1611 said:
can you tell me model nvme? ovh was remove the model nvme on home page

Can't figure out how to tell on ubuntu
02:00.0 Non-Volatile memory controller: Intel Corporation Device 0a53 (rev 02) (prog-if 02 [NVM Express])
Subsystem: Intel Corporation Device 3705

if you look via cache google http://webcache.googleusercontent.com/search?q=cache:https://www.ovh.com/us/&ie=utf-8&oe=utf-8&client=firefox-b-ab will see "NVMe 450 Go Intel® P3520 disks"

willie · April 2017

Does smartctl tell the model number? I wouldn't go by the google cache. If they took P3520 off the page, it might be because they switched to the cheaper 750.

Harambe · April 2017

@willie said:
If they took P3520 off the page, it might be because they switched to the cheaper 750.

I don't think they make a 450GB 750 model, I can only find the 450GB P3520.

FredQc · April 2017

jazz1611 said: can you tell me model nvme? ovh was remove the model nvme on home page

@willie said:
Does smartctl tell the model number? I wouldn't go by the google cache. If they took P3520 off the page, it might be because they switched to the cheaper 750.

root@bhs:~# smartctl -a /dev/nvme0
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.4.49-1-pve] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       INTEL SSDPE2MX450G7
Serial Number:                      CVPF642000AD450RGN
Firmware Version:                   MDV10253
PCI Vendor/Subsystem ID:            0x8086
IEEE OUI Identifier:                0x5cd2e4
Controller ID:                      0
Number of Namespaces:               1
Namespace 1 Size/Capacity:          450,098,159,616 [450 GB]
Namespace 1 Formatted LBA Size:     512
Local Time is:                      Sun Apr 16 14:58:50 2017 EDT
Firmware Updates (0x02):            1 Slot
Optional Admin Commands (0x0006):   Format Frmw_DL
Optional NVM Commands (0x0006):     Wr_Unc DS_Mngmt
Maximum Data Transfer Size:         32 Pages

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +    25.00W       -        -    0  0  0  0        0       0

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         2
 1 -     512       8         2
 2 -     512      16         2
 3 -    4096       0         0
 4 -    4096       8         0
 5 -    4096      64         0
 6 -    4096     128         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning:                   0x00
Temperature:                        22 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    110,583 [56.6 GB]
Data Units Written:                 111,404 [57.0 GB]
Host Read Commands:                 649,283
Host Write Commands:                2,845,072
Controller Busy Time:               4
Power Cycles:                       8
Power On Hours:                     40
Unsafe Shutdowns:                   5
Media and Data Integrity Errors:    0
Error Information Log Entries:      0

Error Information (NVMe Log 0x01, max 64 entries)
No Errors Logged

willie · April 2017

Yes, that appears to be a P3520, thanks.

FredQc · April 2017

root@bhs:~# cd /root
root@bhs:~# dd if=/dev/zero of=test_$$ bs=64k count=16k conv=fdatasync && rm -f test_$$

16384+0 records in
16384+0 records out
1073741824 bytes (1.1 GB) copied, 1.20416 s, 892 MB/s

root@bhs:~# hdparm -tT /dev/md5

/dev/md5:
 Timing cached reads:   37142 MB in  2.00 seconds = 18597.85 MB/sec
 Timing buffered disk reads: 6358 MB in  3.00 seconds = 2119.14 MB/sec

FredQc · April 2017

Hmm... did I made too much tests on these ssds ? Now the system feels weird. Can't execute anything from /usr/bin or /usr/sbin without errors.

    root@bhs:~# apt-get update
    Ign http://debian.bhs.mirrors.ovh.net jessie InRelease
    Hit http://debian.bhs.mirrors.ovh.net jessie-updates InRelease                                                 
    Hit http://debian.bhs.mirrors.ovh.net jessie Release.gpg                                                                                                     
    Hit http://debian.bhs.mirrors.ovh.net jessie Release                                                                                                         
    Get:1 http://debian.bhs.mirrors.ovh.net jessie-updates/main Sources [15.5 kB]                                                                                
    Get:2 http://debian.bhs.mirrors.ovh.net jessie-updates/main amd64 Packages/DiffIndex [7,900 B]                                                               
    Get:3 http://debian.bhs.mirrors.ovh.net jessie-updates/main i386 Packages/DiffIndex [7,900 B]                                                                
    Get:4 http://debian.bhs.mirrors.ovh.net jessie-updates/main Translation-en/DiffIndex [2,704 B]                                                               
    Hit http://security.debian.org jessie/updates InRelease                                                                                                      
    Get:5 http://debian.bhs.mirrors.ovh.net jessie/main Sources [7,056 kB]                                                                   
    Hit http://repo.cloudlinux.com stable InRelease                                                                                                  
    Get:6 http://debian.bhs.mirrors.ovh.net jessie/main amd64 Packages [6,776 kB]                                                                 
    Hit http://security.debian.org jessie/updates/main Sources                                                                                                
    Hit http://security.debian.org jessie/updates/main amd64 Packages                                                                                            
    Hit http://download.proxmox.com jessie InRelease                                                                                                         
    Get:7 http://security.debian.org jessie/updates/main i386 Packages [368 kB]                                                                              
    Get:8 http://debian.bhs.mirrors.ovh.net jessie/main i386 Packages [6,779 kB]                                           
    Get:9 http://debian.bhs.mirrors.ovh.net jessie/main Translation-en [4,582 kB]                                          
    Hit http://repo.cloudlinux.com stable/main amd64 Packages                                                                                
    Get:10 http://debian.bhs.mirrors.ovh.net jessie-updates/main amd64 2017-04-15-2027.16.pdiff [528 B]                                                          
    Failed to exec method /usr/lib/apt/methods/rred
    Get:11 http://debian.bhs.mirrors.ovh.net jessie-updates/main i386 2017-04-15-2027.16.pdiff [527 B]                       
    Failed to exec method /usr/lib/apt/methods/rred
    Get:12 http://security.debian.org jessie/updates/main Translation-en [202 kB]                                            
    E: Method rred has died unexpectedly!                                                                                    
    E: Sub-process rred returned an error code (100)
    E: Method /usr/lib/apt/methods/rred did not start correctly
    E: Method rred has died unexpectedly!
    E: Sub-process rred returned an error code (100)
    E: Method /usr/lib/apt/methods/rred did not start correctly

   root@bhs:~# apt-get install gcc
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    gcc is already the newest version.
    The following packages were automatically installed and are no longer required:
      g++ g++-4.9 libstdc++-4.9-dev
    Use 'apt-get autoremove' to remove them.
    The following packages will be REMOVED:
      dpkg-dev make
    0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
    2 not fully installed or removed.
    After this operation, 3,160 kB disk space will be freed.
    Do you want to continue? [Y/n] y
    (Reading database ... 82113 files and directories currently installed.)
    Removing dpkg-dev (1.17.27) ...
    dpkg: error processing package dpkg-dev (--remove):
     unable to securely remove '/usr/share/man/pl/man1/dpkg-scansources.1.gz.dpkg-tmp': Structure needs cleaning
    Removing make (4.0-8.1) ...
    dpkg: error processing package make (--remove):
     unable to securely remove '/usr/share/locale/be/LC_MESSAGES/make.mo.dpkg-tmp': Structure needs cleaning
    Processing triggers for man-db (2.7.0.2-5) ...
    Errors were encountered while processing:
     dpkg-dev
     make
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    root@bhs:~# apt-get install tk tk-dev
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    Some packages could not be installed. This may mean that you have
    requested an impossible situation or if you are using the unstable
    distribution that some required packages have not yet been created
    or been moved out of Incoming.
    The following information may help to resolve the situation:

    The following packages have unmet dependencies:
     tk-dev:i386 : Depends: tk8.6-dev:i386 (>= 8.6.0-2) but it is not going to be installed
                   Depends: tcl-dev:i386 but it is not going to be installed
    E: Unable to correct problems, you have held broken packages.
    root@bhs:~# cd openlitespeed-1.4.25/
    root@bhs:~/openlitespeed-1.4.25# make
    -bash: /usr/bin/make: No such file or directory
    root@bhs:~/openlitespeed-1.4.25# apt-get install make
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    make is already the newest version.
    The following packages were automatically installed and are no longer required:
      g++ g++-4.9 libstdc++-4.9-dev
    Use 'apt-get autoremove' to remove them.
    The following packages will be REMOVED:
      dpkg-dev make
    0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
    2 not fully installed or removed.
    After this operation, 3,160 kB disk space will be freed.
    Do you want to continue? [Y/n] y
    (Reading database ... 82113 files and directories currently installed.)
    Removing dpkg-dev (1.17.27) ...
    dpkg: error processing package dpkg-dev (--remove):
     unable to securely remove '/usr/share/man/pl/man1/dpkg-scansources.1.gz.dpkg-tmp': Structure needs cleaning
    Removing make (4.0-8.1) ...
    dpkg: error processing package make (--remove):
     unable to securely remove '/usr/share/locale/be/LC_MESSAGES/make.mo.dpkg-tmp': Structure needs cleaning
    Processing triggers for man-db (2.7.0.2-5) ...
    Errors were encountered while processing:
     dpkg-dev
     make
    E: Sub-process /usr/bin/dpkg returned an error code (1)

        root@bhs:~# apt-get autoremove
        Reading package lists... Done
        Building dependency tree       
        Reading state information... Done
        The following packages will be REMOVED:
          dpkg-dev g++ g++-4.9 libstdc++-4.9-dev make
        0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
        2 not fully installed or removed.
        After this operation, 49.1 MB disk space will be freed.
        Do you want to continue? [Y/n] y
        (Reading database ... 82113 files and directories currently installed.)
        Removing dpkg-dev (1.17.27) ...
        dpkg: error processing package dpkg-dev (--remove):
         unable to securely remove '/usr/share/man/pl/man1/dpkg-scansources.1.gz.dpkg-tmp': Structure needs cleaning
        Removing make (4.0-8.1) ...
        dpkg: error processing package make (--remove):
         unable to securely remove '/usr/share/locale/be/LC_MESSAGES/make.mo.dpkg-tmp': Structure needs cleaning
        Removing g++ (4:4.9.2-2) ...
        /var/lib/dpkg/info/g++.prerm: /var/lib/dpkg/info/g++.prerm: cannot execute binary file
        dpkg: error processing package g++ (--remove):
         subprocess installed pre-removal script returned error exit status 126
        /var/lib/dpkg/info/g++.postinst: line 11: /usr/sbin/dpkg-divert: cannot execute binary file: Exec format error
        /var/lib/dpkg/info/g++.postinst: line 20: /usr/sbin/dpkg-divert: cannot execute binary file: Exec format error
        /var/lib/dpkg/info/g++.postinst: line 32: /usr/sbin/update-alternatives: cannot execute binary file: Exec format error
        dpkg: error while cleaning up:
         subprocess installed post-installation script returned error exit status 126
        dpkg: g++-4.9: dependency problems, but removing anyway as you requested:
         g++ depends on g++-4.9 (>= 4.6.4-1~).

        Removing g++-4.9 (4.9.2-10) ...
        Removing libstdc++-4.9-dev:amd64 (4.9.2-10) ...
        dpkg: error processing package libstdc++-4.9-dev:amd64 (--remove):
         cannot remove `/usr/include/c++/4.9/deque': Structure needs cleaning
        Processing triggers for man-db (2.7.0.2-5) ...
        Errors were encountered while processing:
         dpkg-dev
         make
         g++
         libstdc++-4.9-dev:amd64

        E: Sub-process /usr/bin/dpkg returned an error code (1)

-bash: /sbin/xfs_repair: cannot execute binary file: Exec format error

IPMI console giving me I/O errors on XFS filesystem: http://i.imgur.com/ImC88iN.jpg

WTF ...

FredQc · April 2017

Well, I rebooted the node. Complete clusterfuck...

WTF

willie · April 2017

Put in a ticket? I guess those drives might overheat.

FredQc · April 2017

@willie said:
Put in a ticket? I guess those drives might overheat.

Hmm... last time I checked an hour ago it showed 22C

Anyway, I've reinstalled the whole shit

willie · April 2017

FredQc said:

Anyway, I've reinstalled the whole shit

Did that help? I'd still worry.

FredQc · April 2017

@willie said:

FredQc said:

Anyway, I've reinstalled the whole shit

Did that help? I'd still worry.

Yeah, looks fine now. Drives are 21c and 23c respectively.

Proxmox was configured on XFS. Now EXT4.

rndt · April 2017

Just got a SP-64 E3-1270v6 NVMe + 2x2TB in RBX-6.

bench.sh

----------------------------------------------------------------------
CPU model            : Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz
Number of cores      : 8
CPU frequency        : 800.000 MHz
Total size of Disk   : 413.5 GB (152.8 GB Used)
Total amount of Mem  : 64174 MB (792 MB Used)
Total amount of Swap : 1021 MB (0 MB Used)
System uptime        : 0 days, 0 hour 34 min
Load average         : 0.00, 0.00, 0.00
OS                   : Debian GNU/Linux 8
Arch                 : x86_64 (64 Bit)
Kernel               : 4.4.30-mod-std-ipv6-64
----------------------------------------------------------------------
I/O speed(1st run)   : 546 MB/s
I/O speed(2nd run)   : 550 MB/s
I/O speed(3rd run)   : 547 MB/s
Average I/O speed    : 547.7 MB/s
----------------------------------------------------------------------
Node Name                       IPv4 address            Download Speed
CacheFly                        205.234.175.175         26.5MB/s
Linode, Tokyo, JP               106.187.96.148          8.54MB/s
Linode, Singapore, SG           139.162.23.4            6.82MB  
~~~~/s
Linode, London, UK              176.58.107.39           107MB/s
Linode, Frankfurt, DE           139.162.130.8           15.7MB/s
Linode, Fremont, CA             50.116.14.9             15.6MB/s
Softlayer, Dallas, TX           173.192.68.18           4.66MB/s
Softlayer, Seattle, WA          67.228.112.250          10.5MB/s
Softlayer, Frankfurt, DE        159.122.69.4            87.7MB/s
Softlayer, Singapore, SG        119.81.28.170           6.04MB/s
Softlayer, HongKong, CN         119.81.130.170          5.80MB/s
----------------------------------------------------------------------
Node Name                       IPv6 address            Download Speed
Linode, Atlanta, GA             2600:3c02::4b           23.9MB/s
Linode, Dallas, TX              2600:3c00::4b           19.6MB/s
Linode, Newark, NJ              2600:3c03::4b           29.8MB/s
Linode, Singapore, SG           2400:8901::4b           13.9MB/s
Linode, Tokyo, JP               2400:8900::4b           9.04MB/s
Softlayer, San Jose, CA         2607:f0d0:2601:2a::4    11.1MB/s
Softlayer, Washington, WA       2607:f0d0:3001:78::2    1.92MB/s
Softlayer, Paris, FR            2a03:8180:1301:8::4     75.7MB/s
Softlayer, Singapore, SG        2401:c900:1101:8::2     9.28MB/s
Softlayer, Tokyo, JP            2401:c900:1001:16::4    6.13MB/s
----------------------------------------------------------------------


fio --name=rand-write --ioengine=libaio --iodepth=32 --rw=randwrite --invalidate=1 --bsrange=4k:4k,4k:4k --size=512m --runtime=120 --time_based --do_verify=1 --direct=1 --group_reporting --numjobs=8

rand-write: (g=0): rw=randwrite, bs=4K-4K/4K-4K/4K-4K, ioengine=libaio, iodepth=32
...
fio-2.1.11
Starting 8 processes
rand-write: Laying out IO file(s) (1 file(s) / 512MB)
rand-write: Laying out IO file(s) (1 file(s) / 512MB)
rand-write: Laying out IO file(s) (1 file(s) / 512MB)
rand-write: Laying out IO file(s) (1 file(s) / 512MB)
rand-write: Laying out IO file(s) (1 file(s) / 512MB)
rand-write: Laying out IO file(s) (1 file(s) / 512MB)
rand-write: Laying out IO file(s) (1 file(s) / 512MB)
rand-write: Laying out IO file(s) (1 file(s) / 512MB)
Jobs: 8 (f=8): [w(8)] [100.0% done] [0KB/507.1MB/0KB /s] [0/130K/0 iops] [eta 00m:00s]
rand-write: (groupid=0, jobs=8): err= 0: pid=26523: Sun Apr 16 23:14:17 2017
  write: io=59995MB, bw=511943KB/s, iops=127985, runt=120003msec
    slat (usec): min=2, max=58356, avg=13.22, stdev=42.02
    clat (usec): min=0, max=63197, avg=1985.34, stdev=1248.47
     lat (usec): min=16, max=63207, avg=1998.72, stdev=1249.38
    clat percentiles (usec):
     |  1.00th=[  107],  5.00th=[  205], 10.00th=[  298], 20.00th=[  548],
     | 30.00th=[ 1096], 40.00th=[ 2064], 50.00th=[ 2480], 60.00th=[ 2608],
     | 70.00th=[ 2704], 80.00th=[ 2832], 90.00th=[ 3024], 95.00th=[ 3280],
     | 99.00th=[ 4080], 99.50th=[ 5984], 99.90th=[11456], 99.95th=[14016],
     | 99.99th=[15296]
    bw (KB  /s): min=41952, max=87592, per=12.60%, avg=64491.98, stdev=9678.22
    lat (usec) : 2=0.01%, 4=0.01%, 10=0.01%, 20=0.01%, 50=0.11%
    lat (usec) : 100=0.69%, 250=6.60%, 500=10.72%, 750=7.37%, 1000=3.48%
    lat (msec) : 2=10.48%, 4=59.46%, 10=0.94%, 20=0.14%, 50=0.01%
    lat (msec) : 100=0.01%
  cpu          : usr=4.38%, sys=22.79%, ctx=5525411, majf=0, minf=73
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=100.0%, >=64=0.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.1%, 64=0.0%, >=64=0.0%
     issued    : total=r=0/w=15358687/d=0, short=r=0/w=0/d=0
     latency   : target=0, window=0, percentile=100.00%, depth=32

Run status group 0 (all jobs):
  WRITE: io=59995MB, aggrb=511943KB/s, minb=511943KB/s, maxb=511943KB/s, mint=120003msec, maxt=120003msec

Disk stats (read/write):
    md2: ios=0/15363728, merge=0/0, ticks=0/0, in_queue=0, util=0.00%, aggrios=0/15366814, aggrmerge=0/0, aggrticks=0/17696868, aggrin_queue=18005788, aggrutil=96.14%
  nvme0n1: ios=0/15366814, merge=0/0, ticks=0/9420572, in_queue=9614204, util=73.63%
  nvme1n1: ios=0/15366814, merge=0/0, ticks=0/25973164, in_queue=26397372, util=96.14%


dd if=/dev/zero of=test_$$ bs=64k count=16k conv=fdatasync && rm -f test_$$

16384+0 records in
16384+0 records out
1073741824 bytes (1.1 GB) copied, 1.95746 s, 549 MB/s


smartctl -a /dev/sda

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.4.30-mod-std-ipv6-64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     HGST HUS726020ALA610
Serial Number:    K5H2U8DA
LU WWN Device Id: 5 000cca 25ecf5f1c
Firmware Version: A5GNT920
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Apr 16 23:18:38 2017 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   054    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   100   100   024    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       7
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       6
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       7
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       7
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       7
194 Temperature_Celsius     0x0002   187   187   000    Old_age   Always       -       32 (Min/Max 20/33)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%         2         -
# 2  Short offline       Completed without error       00%         2         -
# 3  Short offline       Completed without error       00%         1         -
# 4  Short offline       Completed without error       00%         0         -


nvme smart-log /dev/nvme0n1

Smart Log for NVME device:nvme0n1 namespace-id:ffffffff
critical_warning                    : 0
temperature                         : 25 C
available_spare                     : 100%
available_spare_threshold           : 10%
percentage_used                     : 0%
data_units_read                     : 135,380
data_units_written                  : 217,317
host_read_commands                  : 603,897
host_write_commands                 : 16,857,403
controller_busy_time                : 1
power_cycles                        : 14
power_on_hours                      : 39
unsafe_shutdowns                    : 0
media_errors                        : 0
num_err_log_entries                 : 0
Warning Temperature Time            : 0
Critical Composite Temperature Time : 0


nvme smart-log /dev/nvme1n1

Smart Log for NVME device:nvme1n1 namespace-id:ffffffff
critical_warning                    : 0
temperature                         : 28 C
available_spare                     : 100%
available_spare_threshold           : 10%
percentage_used                     : 0%
data_units_read                     : 134,456
data_units_written                  : 217,317
host_read_commands                  : 593,562
host_write_commands                 : 16,857,411
controller_busy_time                : 2
power_cycles                        : 14
power_on_hours                      : 39
unsafe_shutdowns                    : 0
media_errors                        : 0
num_err_log_entries                 : 0
Warning Temperature Time            : 0
Critical Composite Temperature Time : 0


sensors

acpitz-virtual-0
Adapter: Virtual device
temp1:        +27.8°C  (crit = +119.0°C)
temp2:        +29.8°C  (crit = +119.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +34.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:         +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 1:         +34.0°C  (high = +80.0°C, crit = +100.0°C)
Core 2:         +32.0°C  (high = +80.0°C, crit = +100.0°C)
Core 3:         +31.0°C  (high = +80.0°C, crit = +100.0°C)

https://browser.geekbench.com/v4/cpu/2562969

Harambe · April 2017

@FredQc Still having issues with those NVMe drives? Looking at either the SP64 or EG32 - 2xHDD 2xNVMe to replace my current EG-16 2xHDD.

FredQc · April 2017

@Harambe said:
@FredQc Still having issues with those NVMe drives? Looking at either the SP64 or EG32 - 2xHDD 2xNVMe to replace my current EG-16 2xHDD.

These NVMes runs perfectly fine with the E3-1270v6. I would not worry ;-)

Howdy, Stranger!

Categories

In this Discussion

OVH New SP-32 and SP-64 2017 with E3-1270v6 4c/8th 3.8/4.2GHz and vRack!

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

OVH New SP-32 and SP-64 2017 with E3-1270v6 4c/8th 3.8/4.2GHz and vRack!

Comments