By using this site, you agree to our Privacy Policy and our Terms of Use. Close
Intrinsic on 05 November 2017
Edit Thread
Pemalite said:
Intrinsic said:

Yes thats because on the PS4 the I/O bus is basically a SATA 2 lane. That means that anything you conect to that bus will be sharing that 600MB/s max limit. 

Ideally, that bus should have been a PCIE bus which would have meant that all connected devices have a pool of 4GB/s (depending on what kinda PCIE lane is used) to share from. But those PCIE lanes makes the MB cost more to make.

Sata 2 is limited to 300MB/s. Not 600MB/s.

The Playstation 4 Pro is using Sata 3.
My bad... mixing up my sata bandwiths.....

Intrinsic said:

  1. When talking about the SATA interface, you basically have mechanical drives or SSDs or hybrids (SSHD), but whats important there is the interface which peaks at a theoretical 600MB/s.

Not a real limitation as the majority of Mechanical Disks, heck even probabably SSHD's are not going to be pushing past that 600MB/s barrier.

Heck there are even a heap of budget SSD's (That a console is more likely to use) that wouldn't either.

The other issue is of course... External Hard Drives. This generation has almost necessitated their use (I have two 4 Terabyte drives dangling off the Xbox), next gen will only exacerbate the problem.
An Internal SSD is NOT going to assist in that regard.

But... If Microsoft/Sony were to include some NAND on the motherboard to cache *all* drives (Optical, Internal and External) then that is a better approach overall, don't you think?

But thats exactly my point though... and why I even listed the bandwith as 500MB/s.... in hindsight I should have put ~500MB/s. Thats because its really hard to find anything that averages that theoretical bandwith. Not just with SATA but anything for that matter. Hence why its called a theoretical limit.

The cache thing seems like a great idea.... but wouldn't that just make the console more expensive to make. Or does that allow them cheap out on what kinda internal drive they would use? So maybe have something like 128GB/256GB internal cache over a PCIex4 lane?

Wouldn't it be just better to stick in an M.2 drive at the end of that instead?

Oh, and that last point, wouldn't taht be kinda like the NS setup (or the embedded option in the OP)? Have some sort of embedded cache but all users connect a standard SATA drive to the console. The console will probably come with one anyways.

Last edited by Intrinsic - on 05 November 2017