KingSpec SSD分区


0

我最近买了一台KSD-PA25.6-064MS,它预先格式化,分区从63区开始。

我知道这对于SSD来说并不典型,并且可能导致过多的写入放大。但是,由于这是制造商所做的,因此可能会针对此特定布局进行专门设计。

制造商网站上的规格并未说明擦除块等。同样,我还没有直接联系制造商 - 他们网站上指定的频道似乎无法正常工作。

有没有人做过性能测试或者其他什么来找出内部参数,特别是上面提到的问题?

对SSD结构的一般信息不感兴趣。我对KingSpec驱动器特别感兴趣(离我的模型越近越好) - 如果它们是特殊的或者不是。

Answers:


1

我最终没有得到制造商的任何答复,即使我给他们的海外销售经理(他们网站上唯一证明有效的联系渠道)做了CC,他把我的信息转发给了一个相应的部门,要求他们回复它。

根据为可能的分区调整确定SSD的内部扇区大小 - PC评论新闻组,KingSpec驱动器使用股票第三方闪存芯片(正如预期的更低价格段产品) - 因此任何不寻常的内部构件的可能性非常小。

根据 flashbench输出:

$ flashbench -a /dev/sda -b 1024
align 536870912 pre 547Вµs  on 702Вµs   post 528Вµs diff 164Вµs
align 268435456 pre 540Вµs  on 700Вµs   post 544Вµs diff 158Вµs
align 134217728 pre 565Вµs  on 717Вµs   post 531Вµs diff 168Вµs
align 67108864  pre 571Вµs  on 727Вµs   post 547Вµs diff 168Вµs
align 33554432  pre 554Вµs  on 732Вµs   post 554Вµs diff 178Вµs
align 16777216  pre 568Вµs  on 664Вµs   post 551Вµs diff 104Вµs
align 8388608   pre 575Вµs  on 644Вµs   post 590Вµs diff 61.2Вµs
align 4194304   pre 576Вµs  on 644Вµs   post 590Вµs diff 60.9Вµs
align 2097152   pre 576Вµs  on 645Вµs   post 591Вµs diff 61.5Вµs
align 1048576   pre 577Вµs  on 646Вµs   post 591Вµs diff 61.8Вµs
align 524288    pre 576Вµs  on 646Вµs   post 593Вµs diff 61.5Вµs
align 262144    pre 575Вµs  on 646Вµs   post 590Вµs diff 62.8Вµs
align 131072    pre 583Вµs  on 649Вµs   post 574Вµs diff 70.3Вµs
align 65536 pre 585Вµs  on 653Вµs   post 582Вµs diff 70Вµs
align 32768 pre 586Вµs  on 652Вµs   post 580Вµs diff 68.7Вµs
align 16384 pre 584Вµs  on 624Вµs   post 586Вµs diff 39.4Вµs
align 8192  pre 586Вµs  on 605Вµs   post 587Вµs diff 19Вµs
align 4096  pre 585Вµs  on 605Вµs   post 586Вµs diff 19.4Вµs
align 2048  pre 584Вµs  on 584Вµs   post 585Вµs diff 379ns 

我的驱动器使用16K扇区和16M擦除块。

现在,让我们看看分区的时间:

$ flashbench -a /dev/sda1 -b 1024
align 536870912 pre 690Вµs  on 671Вµs   post 722Вµs diff -35600n
align 268435456 pre 707Вµs  on 683Вµs   post 734Вµs diff -37774n
align 134217728 pre 691Вµs  on 672Вµs   post 724Вµs diff -36217n
align 67108864  pre 711Вµs  on 688Вµs   post 741Вµs diff -37954n
align 33554432  pre 717Вµs  on 694Вµs   post 746Вµs diff -37195n
align 16777216  pre 714Вµs  on 692Вµs   post 744Вµs diff -36476n
align 8388608   pre 759Вµs  on 736Вµs   post 786Вµs diff -36996n
align 4194304   pre 757Вµs  on 732Вµs   post 782Вµs diff -37075n
align 2097152   pre 758Вµs  on 733Вµs   post 783Вµs diff -38152n
align 1048576   pre 757Вµs  on 735Вµs   post 788Вµs diff -37275n
align 524288    pre 759Вµs  on 736Вµs   post 786Вµs diff -36078n
align 262144    pre 754Вµs  on 733Вµs   post 789Вµs diff -38073n
align 131072    pre 738Вµs  on 718Вµs   post 766Вµs diff -33265n
align 65536 pre 747Вµs  on 728Вµs   post 773Вµs diff -32086n
align 32768 pre 745Вµs  on 725Вµs   post 776Вµs diff -35799n

WTF?没有图案和负面差异?实际上,这表明读取不与SSD块对齐。

实际上,如果我将分区开始更改为扇区64,则输出更改为更期望的:

$ flashbench -a /dev/sda1 -b 1024
align 536870912 pre 531Вµs  on 600Вµs   post 530Вµs diff 69.3Вµs
align 268435456 pre 543Вµs  on 611Вµs   post 542Вµs diff 68.4Вµs
align 134217728 pre 531Вµs  on 600Вµs   post 531Вµs diff 68.9Вµs
align 67108864  pre 548Вµs  on 618Вµs   post 548Вµs diff 69.8Вµs
align 33554432  pre 555Вµs  on 624Вµs   post 553Вµs diff 70.4Вµs
align 16777216  pre 552Вµs  on 622Вµs   post 552Вµs diff 69.9Вµs
align 8388608   pre 594Вµs  on 664Вµs   post 592Вµs diff 71.1Вµs
align 4194304   pre 593Вµs  on 660Вµs   post 590Вµs diff 68.7Вµs
align 2097152   pre 590Вµs  on 660Вµs   post 593Вµs diff 69.1Вµs
align 1048576   pre 593Вµs  on 665Вµs   post 595Вµs diff 71.6Вµs
align 524288    pre 594Вµs  on 663Вµs   post 591Вµs diff 70.1Вµs
align 262144    pre 593Вµs  on 664Вµs   post 594Вµs diff 70.5Вµs
align 131072    pre 578Вµs  on 643Вµs   post 577Вµs diff 65.4Вµs
align 65536 pre 583Вµs  on 650Вµs   post 577Вµs diff 70Вµs
align 32768 pre 583Вµs  on 654Вµs   post 587Вµs diff 68.8Вµs
align 16384 pre 581Вµs  on 623Вµs   post 584Вµs diff 40.4Вµs
align 8192  pre 583Вµs  on 601Вµs   post 582Вµs diff 17.9Вµs
align 4096  pre 582Вµs  on 601Вµs   post 583Вµs diff 19Вµs
align 2048  pre 581Вµs  on 581Вµs   post 581Вµs diff -479ns
By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.