From: thelma@sys-concept.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Performance: WD vs. Samung SSD vs. M.2 SSD
Date: Tue, 1 Dec 2020 20:58:07 -0700 [thread overview]
Message-ID: <e0ace6fc-ac64-fde0-caf1-a0b87a648b55@sys-concept.com> (raw)
In-Reply-To: <7cef0507.149c4.176218a592d.Coremail.bobwxc@88.com>
On 12/01/2020 08:41 PM, bobwxc wrote:
>> ------------------ 原始邮件 ------------------
>> 发 件 人：thelma@sys-concept.com
>> 发送时间：2020-12-02 05:46:56
>> 收 件 人："Gentoo mailing list" <gentoo-user@lists.gentoo.org>
>> 抄 送：
>> 主 题：[gentoo-user] Performance: WD vs. Samung SSD vs. M.2 SSD
>>
>> Nothing scientific, but I was surprised how fast M.2 disk is, so decided to
>> time how fast GnuCash will load my accounting, here it is:
>>
>> Box 1.)
>> WD (spinning disk) CPU AMD-8150 (8-core), 16GiB
>> Time to open GnuCash - 23sec.
>>
>> Box 2.)
>> Samsung SSD 850, CPU AMD Ryzen 5 1400 Quad-Core, 16GiB
>> Time to open GnuCash - 15sec.
>>
>> Box 3.)
>> M.2 SSD, CPU AMD Ryzen 7, 32Gib
>> Time to open GnuCash - 2.5sec
> SATA Revision 3.0 -- 6Gbps
> NVMe -- PCI-E3.0*4 -- 7.877 Gbps*4
>
>
>
>
> NVMe is much faster than AHCI
This is nvme Force MP600 (SSD Interface. PCIe Gen 4.0 x4)
SSD Max Sequential Read CDM. Up to 4,950MB/s.
SSD Max Sequential Write CDM. Up to 4,250MB/s.
Vs.
Samsung SSD 850 evo
sequential write speeds up to 520 MB/s
sequential read speeds up to 540 MB/s
next prev parent reply other threads:[~2020-12-02 3:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 21:46 [gentoo-user] Performance: WD vs. Samung SSD vs. M.2 SSD thelma
2020-12-01 21:57 ` thelma
2020-12-02 3:41 ` bobwxc
2020-12-02 3:58 ` thelma [this message]
2020-12-02 18:33 ` Frank Steinmetzger
2020-12-02 19:45 ` Rich Freeman
2020-12-02 21:03 ` thelma
2020-12-02 23:14 ` Peter Humphrey
2020-12-02 23:49 ` thelma
2020-12-03 0:09 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e0ace6fc-ac64-fde0-caf1-a0b87a648b55@sys-concept.com \
--to=thelma@sys-concept.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox