Performance issue with new intel 660p 1tb

[bonehead123]

"cheap is as cheap does"

'nuff said.......

 

[londiste]

"cheap is as cheap does"
'nuff said.......

Reads are reliably fast and price undercuts even SATA drives... performance/$ is very-very good in 660p.
200TBW for 1TB and 400TBW for 2TB models are reasonable enough numbers given that Intel decided to put these into specs. Alleviates some of the concerns about endurance.

 

[gasolin]

Theres no difference from 8mb to 64 mb

Changing Queu Depth

Queue depth is the number of I/O requests (SCSI commands) that can be queued at one time on a storage controller. Each I/O request from the host's initiator HBA to the storage controller's target adapter consumes a queue entry. Typically, a higher queue depth equates to better performance.

So the storage controller is ?

I though of call it a day and buy a 2tb samsung 970 pro, guess what, they only make a 2tb samsung 970 evo and evo plus.

WHY?

 

[theonek]

Evo plus is the model for you, it's faster than Pro though...

 

[gasolin]

1 or 2 tb ? i think 2tb since it makes more sense although extreme expensive

 

[TheLostSwede]

Something is screwy with that SSD of yours. Did you look to see if there's a firmware update?

 

[londiste]

Did a few more tests with ATTO on my 2TB 660p. With 512MB file size, at around the 8MB I/O Size test, drive temperature reached 70C and it seems to start throttling around that.
Someone said it in the beginning of the thread as well - try monitoring the drive temperature while running ATTO.

 

[gasolin]

No firmware update

To my surprise i fixed my low seq score in AS SSD Benchmark (#49) only by updating to latest version of ASS SSD Benchmark

ATTO wanna upgrade my ssd, even 154 gb more free space (500gb + ) didn't make a difference

Did a few more tests with ATTO on my 2TB 660p. With 512MB file size, at around the 8MB I/O Size test, drive temperature reached 70C and it seems to start throttling around that.
Someone said it in the beginning of the thread as well - try monitoring the drive temperature while running ATTO.

My intel 660p 1tb has never been hotter than 41c under my heatsink (no sticker), it's just insane that a samsung 970 evo plus is as expensive as a medium priced (europe) rtx 2070 or one of the most expensive rtx 2060 super.

 

[newtekie1]

You're worrying about a benchmark that doesn't equate to real world performance. Seriously, ATTO(especially at file sizes larger than 8MB) doesn't apply to most PC users and really doesn't affect the real world performance of a system drive.

Is the system responsive and fast? If yes, then leave it alone and just enjoy the nice fast system. People need to stop worrying about benchmark scores.

 

[gasolin]

Tried update (aut) in device manager(almost never in 10 years i have had a new driver this way), didn't seem to find any new driver (was doing something else, didn't give device manager my full attention)

storage device controller was intel 660p , after it was done searching it asked me if i wanted to reboote for the change to be enabled (the usually do you want to reeboote), i did that a few min later now storage device controller say intel (R) NVMe Controller

I used windows update, manually looked at intels website, driver boost, slim driver,snaildriver yesterday and today, didn't find any new driver for my intel 660p i was shure would be something i should install

Her are the updates after my reboote

Look at the left corner, old bencmark IaNVMe new benchmark iaStorAC, something has changed

You're worrying about a benchmark that doesn't equate to real world performance. Seriously, ATTO(especially at file sizes larger than 8MB) doesn't apply to most PC users and really doesn't affect the real world performance of a system drive.

Is the system responsive and fast? If yes, then leave it alone and just enjoy the nice fast system. People need to stop worrying about benchmark scores.

Wouldn't a non perfect benchmark tell you if something is not up to date?

 

[EarthDog]

Look at the left corner, old bencmark IaNVMe new benchmark iaStorAC, something has changed

That's the NVMe driver versus what windows installs natively/Intel IRST IIRC.....

 

[er557]

Per the nvme driver, I tried to update my sx8200 pro adata to the silicon motion generic driver, same controller as other supported drive, it updated fine in device manager, however windows became unbootable. So what is the proper way to update mfgr driver of nvme boot drive without rendering OS unbootable? I would think macrium reflect resuce cd usage, and choose redeploy on new hardware, so it updates the needed files of the OS offline??

 

[gasolin]

Per the nvme driver, I tried to update my sx8200 pro adata to the silicon motion generic driver, same controller as other supported drive, it updated fine in device manager, however windows became unbootable. So what is the proper way to update mfgr driver of nvme boot drive without rendering OS unbootable? I would think macrium reflect resuce cd usage, and choose redeploy on new hardware, so it updates the needed files of the OS offline??

I can't help you there, i just wanted to see what my device manager said about my nvme ssd and about the driver, tried update (search for it aut) it found something, had to reboote for the driver,update to kick in since ATTO benchmark was the same untill i rebooted

Now all of my ssd bencmarks are normal That's just what i wanted, why shouldn't it be able to take ATTO Benchmark with as normal result as a samsung 970 evo plus besides the naturally lower score do to being a low budget nvme sdd.

 

[kapone32]

Per the nvme driver, I tried to update my sx8200 pro adata to the silicon motion generic driver, same controller as other supported drive, it updated fine in device manager, however windows became unbootable. So what is the proper way to update mfgr driver of nvme boot drive without rendering OS unbootable? I would think macrium reflect resuce cd usage, and choose redeploy on new hardware, so it updates the needed files of the OS offline??

Macrium is actually a great tool. Unfortunately you may have bricked your drive. As even though they use the same controller there may be differences in the NAND flash type used. The best thing to do is get the driver form the actual manufacturers website but Adata only has the daatsheet to download form there website. Outside of that there is not many options other than Windows update or using a another drive to install Windows and then roll back the drivers for the AData drive.

 

[newtekie1]

Wouldn't a non perfect benchmark tell you if something is not up to date?

There is no such thing as a perfect benchmark. Especially not on a system drive that is constantly in use by Windows.

 

[er557]

Macrium is actually a great tool. Unfortunately you may have bricked your drive. As even though they use the same controller there may be differences in the NAND flash type used. The best thing to do is get the driver form the actual manufacturers website but Adata only has the daatsheet to download form there website. Outside of that there is not many options other than Windows update or using a another drive to install Windows and then roll back the drivers for the AData drive.

I didn't brick anything, just used boot menu "last known good configuration" which I prepared in advance on my pc, (google it) , and voila- the generic driver was back and windows booted.
However, I didnt touch the firmware so as to brick it, just the driver, and controller being the same, I dont see why it wouldn't work for say non boot drive. the issue was with windows boot driver config, not the drive itself. BTW, it works fine now on the generic windows drv.

 

[kapone32]

I didn't brick anything, just used boot menu "last known good configuration" which I prepared in advance on my pc, (google it) , and voila- the generic driver was back and windows booted.
However, I didnt touch the firmware so as to brick it, just the driver, and controller being the same, I dont see why it wouldn't work for say non boot drive. the issue was with windows boot driver config, not the drive itself. BTW, it works fine now on the generic windows drv.

Nice that is good to hear. I get what you are saying but as I said you should never use another company's driver on an NVME drive regardless of boot or storage as there may be particulars like RAM size and NAND type or density and firmware.

 

[er557]

True, there are particulars, but you are missing the point here, this is about a WINDOWS driver for the nvme CONTROLLER, not firmware or deep hardware usage of the drive. So regardless of capacity, nand and ram, a controller driver can be used in WINDOWS to talk to the drive. This is not the same as say a gpu bios. I actually used the official driver from silicon motion, not another drive's driver. Even if I would have, it wouldnt have bricked the drive, it also would not install in device manager due to different hardware id.