Ass of Can Whooping
Member
What do you mean? where did I add and subtract? It's 2GB of data at 5GB/s divided by a compression factor of 1.5 to get 0.2666 seconds.
Using the 7 - 9 figure for the PS5 and the 6GB figure for the XSX
What do you mean? where did I add and subtract? It's 2GB of data at 5GB/s divided by a compression factor of 1.5 to get 0.2666 seconds.
I got the 7-9 GB/s from Cerny's presentation road to PS5. Maybe I misheard. The 4.8 -6Gb/s was from MSFT. And it is Sony that mentioned the theoretical high of 22GB/s for specific data. We have heard no such thing from MSFT.Wrong again.
You try to downplay PS5 compression at the same time you overestimate the Xbox one.
There is no 7-9GB/s... stop to made up... there is 8-9GB/s that is what Sony devs got in typical cases.
MS shared 4.8GB/s that already include the use of BCPack... Zlib can't reach 50% compression sorry.
That 6GB/s is the same as PS5's 22GB/s... best case scenario with very specific type of data.
Still running on the assumption that developers will do absolutely nothing to improve Kraken compression, I see...Okay so thank you for the clarification but the point still stands. Because I was using the 9GB/s rate not the lower one. Otherwise the figures to compare are:
PS5:
8-9 GB/s
XSX:
4.8-6GB/s before XBTC is finalized.
That's not what I was calculating in the comment you replied to. In any case I was using 6GB for the XSX and 9GB for the PS5. Never considered the 7GB/s which is actually 8GB/s. On the other hand if we compare 4.8 to 8, its still a solid reduction of 50% over the original 200% advantage in raw read write speeds.Using the 7 - 9 figure for the PS5 and the 6GB figure for the XSX
Fixed with reality.PS5:
8-9GB/s
XSX:
4.8GB/s
Reality check again.So the final figures are:
PS5:
8-9GB/s
XSX(Before BCPack finalized):
4.8GB/s
You can predict whatever dream scenario you want.My prediction After XBTC finalized:
XSX:
5-6GB/s
What developers are you talking about??Still running on the assumption that developers will do absolutely nothing to improve Kraken compression, I see...
Yes it does factor BCPack... zlib alone won't provide a 50% compression ratioThe 4.8GB/s doesn't factor in BCPack!! They're still working on it to increase the throughput.
It might go higher but the figures MS gave with BCPack included show 50% compression 2.4/s->4.8GB/sWhy are you using 50% yet BCPack is being optimized to go higher than that? A
I remember reading an article that went over this, you'll essentially need to write PBs worrth of data, other components are likely to fail before the SSDBut did they solve the issue with the write limits on SSDs?
It doesNope the 4.8GB/s figure does not factor in BCPack.
6GB/s is a theoretical limit of the hardware decompressing block, for reference the theoretical limit of PS5 decompression block is 22GB/s.The 6GB/s does
I have no qualms with that. I corrected him for using the hardware decompressing block theoretical limit (6GB/s) as a typical figureGotta give it to rntongo on this one at least regarding the BCPack optimization; one of the XSX team members mentioned on Twitter in responses that they are still looking to push the compression effectiveness further.
What developers are you talking about??
Fixed again.PS5:
8-9 GB/s
XSX:
4.8GB/s before XBTC is finalized.
Still running on the assumption that developers will do absolutely nothing to improve Kraken compression, I see...
Fixed with reality.
I was expecting Sony to hit 12-13GB/s such that they can load up all of RAM for gaming instantly. But they don't need to and it seems MSFT has achieved better compression ratios. Because they have 4.8-6GB/s before even XBTC is finalized. At this point these ranges are unlikely to changeSo if they improve Krakens decompression could they reach something like 11 gb/s to 13 gb/s?
I'm really curious as to how it works.
I was expecting Sony to hit 12-13GB/s such that they can load up all of RAM for gaming instantly. But they don't need to and it seems MSFT has achieved better compression ratios. Because they have 4.8-6GB/s before even XBTC is finalized. At this point these ranges are unlikely to change
So if they improve Krakens decompression could they reach something like 11 gb/s to 13 gb/s?
I'm really curious as to how it works.
Fixed with reality.
Reality check again.
Fixed.
You can predict whatever dream scenario you want.
Ethomaz Defence Force is already on track!Fixed again.
It's actually slightly above that so we'll know once XBTC is done.Did Microsoft announce 6GB/s someplace?
I remember reading about the 4.8 GB/s figure but I don't remember them making the claim of 6GB/s.
Maybe you could provide me with a source so I can read about it?
Our second component is a high-speed hardware decompression block that can deliver over 6GB/s
They don't.I was expecting Sony to hit 12-13GB/s such that they can load up all of RAM for gaming instantly. But they don't need to and it seems MSFT has achieved better compression ratios. Because they have 4.8-6GB/s before even XBTC is finalized. At this point these ranges are unlikely to change
Very mature response!They don't.
Stop the bullshit.
I tried to explain we have the data backing up but the guy keep talking about 7-9GB/s (decrease the realista) and 4.8-6GB/s (increase the reality) for obvious reasons.Ethomaz Defence Force is already on track!
To save our mother GAF from any SSDs attack!
From vicious giant Xbox who once again come back!
He'll unleash all his forces, he wont cut them any slack!
Be ready for a needed reality check!
The EDF deploys!
Thanks... different from your with false data.Very mature response!
"Can" is rather different from "Will".It's actually slightly above that so we'll know once XBTC is done.
Here is the quote from Andrew Gossen:
And here is the link:
https://www.eurogamer.net/articles/digitalfoundry-2020-inside-xbox-series-x-full-specs
It's actually slightly above that so we'll know once XBTC is done.
Here is the quote from Andrew Gossen:
And here is the link:
https://www.eurogamer.net/articles/digitalfoundry-2020-inside-xbox-series-x-full-specs
Where do you get the 5-6 from? MS officially said max is 4.8.What developers are you talking about? Do you understand that the Kraken Decompression is hardware accelerated? And game developers won't have anything to do with it. Sony has optimized the hardware and software for decompression and the results have been 7-9GB/s. MSFT is using a different approach with a higher emphasis on Software than Sony and they haven't yet finalized the BCPack software. Once it's done there's no reason going back unless they can do something major. Which is unlikely to happen for either consoles.
So the final figures are:
PS5:
7-9GB/s
XSX(Before BCPack finalized):
4.8-6GB/s
My prediction After XBTC finalized:
XSX:
5-6GB/s
Your own link official specs.It's actually slightly above that so we'll know once XBTC is done.
Here is the quote from Andrew Gossen:
And here is the link:
https://www.eurogamer.net/articles/digitalfoundry-2020-inside-xbox-series-x-full-specs
It's nice to brag about the speed of decompression, but what does it REALLY bring to the table? In order to decompress something it must be read from somewhere. No SSD at this point in time can reach anywhere near 22 GB/s speeds.6GB/s is a theoretical limit of the hardware decompressing block, for reference the theoretical limit of PS5 decompression block is 22GB/s.
The SSD is actually transferring at 5.5GB in one second max it just the end result after decompression is typically 8-9GB.It's nice to brag about the speed of decompression, but what does it REALLY bring to the table? In order to decompress something it must be read from somewhere. No SSD at this point in time can reach anywhere near 22 GB/s speeds.
This is basically the equivalent of comparing PCIe 3.0 and PCIe 4.0. At x16 the former is max 32GB/s and the latter is max 64GB/s. How much is the difference in games? Less than 1% difference in framerate. Even PCIe 2.0 x16, which is max 16GB/s, gives about 2% less frames on average compared to the 64GB/s PCIe 4.0, max about 5%-7% less.
Yeah yeah, we can't compare PCs blah blah, because the consoles defy physics...
Edit: I'm getting some questions in my head. I'm going to listen to Cerny again.
Where do you get the 5-6 from? MS officially said max is 4.8.
Sorry. We're not ready to share more publicly, but we have revealed more to Xbox licensees. I am actively improving the Xbox Texture Compressor (XBTC) and will be sharing frequent updates with the Xbox community as they come.
They are still working on the texture compression so their overall compression ratio will be higher for the lower range(2.4/4.8=0.5).
Here is the tweet
They have already built a hardware decompression block. Sony has built an impressive system able to achieve a throughput of 8-9GB/s. MSFT has done good as well with what seems to be higher compression ratio. MSFT is relying more on software but even then the figures of 4.8-6GB/s are looking final at this point.Still running on the assumption that developers will do absolutely nothing to improve Kraken compression, I see...
They are still working on the texture compression so their overall compression ratio will be higher for the lower range(2.4/4.8=0.5).
Here is the tweet
A decompression block does decompressing. The chip has no influence on the __compression ratio. If you actually listened, Cerny said that if the data is compressed particularly well, then the speed can go up to 22 GB/s. If you actually go to RAD Gametools's website, their updates talk about improving the compression ratio on Kraken.They have already built a hardware decompression block. Sony has built an impressive system able to achieve a throughput of 8-9GB/s. MSFT has done good as well with what seems to be higher compression ratio. MSFT is relying more on software but even then the figures of 4.8-6GB/s are looking final at this point.
This is what gets me. The people who repeatedly mocked the "SSD secret sauce" even though no one actually referred to the PS5's SSD as "secret sauce" have basically admitted that the SSD is important after all.A couple of weeks ago you love to told us the SSD doesn't matter only flops matter but now what happens ?
And what do you base that on? That they showed quickly changing between different games requires just a few seconds of loading, and that older Xbox games without any adaptation load a lot faster, does not somehow mean that the XSX does not have zero loading screens in mind for the games that are developed specifically for the XSX console.You all realise the SSD isn't the only component in the PS5 that is aimed at removing load times
PS5 Goal - Remove load screens
XSX Goal - Reduce load screens
Both have different overall goals and removing load times wasn't one for XSX.
It's nice to brag about the speed of decompression, but what does it REALLY bring to the table? In order to decompress something it must be read from somewhere. No SSD at this point in time can reach anywhere near 22 GB/s speeds.
This is basically the equivalent of comparing PCIe 3.0 and PCIe 4.0. At x16 the former is max 32GB/s and the latter is max 64GB/s. How much is the difference in games? Less than 1% difference in framerate. Even PCIe 2.0 x16, which is max 16GB/s, gives about 2% less frames on average compared to the 64GB/s PCIe 4.0, max about 5%-7% less.
Yeah yeah, we can't compare PCs blah blah, because the consoles defy physics...
Edit: I'm getting some questions in my head. I'm going to listen to Cerny again.
not official
Yea Cerny said they're looking to remove all bottlenecks everywhere. I hope that works out great.You all realise the SSD isn't the only component in the PS5 that is aimed at removing load times
PS5 Goal - Remove load screens
XSX Goal - Reduce load screens
Both have different overall goals and removing load times wasn't one for XSX.
Think about what Cerny said about only loading what's visible to the player and what the player may see in the next second. Loading time is barely surface level. The faster the SSD, the less seconds' worth of data the system needs to load. That frees up more memory for things such as more detailed assets.You all realise the SSD isn't the only component in the PS5 that is aimed at removing load times
PS5 Goal - Remove load screens
XSX Goal - Reduce load screens
Both have different overall goals and removing load times wasn't one for XSX.
Optimization can mean just few MBs worth or fine tuning it to ensure 4.8GB/s most of the time. As others have said its in MS best interests to present their solution in the best possible light, i would advise caution in expecting higher numbers than they advertised.MSFT still optimizing texture compression
Unless they optimize below 4.8GB/s which would be absurd, it should be higher and at least hit the 5GB/s PS5 target or even go higher closer to the 6GB/s they have marketed thus far.
Thats the decompression hardware block theoretical max, its physical limit. Just like PS5s 22GB/s
Im not bragging about a theoretical peak of the hardware decompression block, I understand what peak means. Im using it as a reference to explain precisely that.It's nice to brag about the speed of decompression, but what does it REALLY bring to the table? In order to decompress something it must be read from somewhere. No SSD at this point in time can reach anywhere near 22 GB/s speeds.
The video is playing yet but it is from a Fake account.Video pulled? Why?
Hey did it earlier today with the mandolorian 2 trailer.That's some bizarre viral marketing. Usually you don't see that from IGN where people go for actual gaming news.
lol Why are you considering 6GB/s for Series X and not 22GB/s for PS5?I got the 7-9 GB/s from Cerny's presentation road to PS5. Maybe I misheard. The 4.8 -6Gb/s was from MSFT. And it is Sony that mentioned the theoretical high of 22GB/s for specific data. We have heard no such thing from MSFT.
Okay so thank you for the clarification but the point still stands. Because I was using the 9GB/s rate not the lower one. Otherwise the figures to compare are:
PS5:
8-9 GB/s
XSX:
4.8-6GB/s before XBTC is finalized.
Sony is not using a software approach like MSFT. Or to the extent of MSFT. Their Decompression algorithms are in a hardware block and that's where it ends. MSFT on the other hand is using a combination of software and hardware. Same thing with the File IO, mapping, Backwards Compatibility. The two companies are using different approaches.Optimization can mean just few MBs worth or fine tuning it to ensure 4.8GB/s most of the time. As others have said its in MS best interests to present their solution in the best possible light, i would advise caution in expecting higher numbers than they advertised.
Likewise you can rest assured Sony is still optimizing their compression algorithms but don't go expecting 20GB/s outside of edge cases if at all
Thats the decompression hardware block theoretical max, its physical limit. Just like PS5s 22GB/s
Im not bragging about a theoretical peak of the hardware decompression block, I understand what peak means. Im using it as a reference to explain precisely that.
That being said the point of compression is to get more data in memory than the raw output can provide. There might be 20-22GB worth of data that can compress to 5.5GB in a very specific edge case. Just like there might be 6GB worth of data that can compress to 2.4GB in a specific edge case.
These peak figures aren't the norm, and you won't see them in regular gaming scenarios
To tell me "nobody but you claims SSD outputs 22GB/s" is a ridiculous statement. Where did I say it did? I said no SSD today outputs 22GB/s.If numbers are about compression(and not raw speed), why would SSD be read at 22GB/s speed?
compressed data -> read it at 5.5GB/s -> uncompress -> now it is "20GB of data"
I think that numbers mean this.
Nobody (but you) claims that SSD outputs 22GB/s, as smaller compressed data which is read from it uncompressed into these bigger numbers.
If they could read SSD at 22GB/s then theoretical number for compressed would be still higher than that.
And this 22 figure is just in theory for data that compress really well so it is not expected to happen 100% of the time anyway
lulwut? if Sony isn't using software what is Kraken?MSFT on the other hand is using a combination of software and hardware. Same thing with the File IO, mapping, Backwards Compatibility.
So why you expecting something different than 4.8GB/sThe ranges they gave are unlikely to go higher or lower at this point.
I repeat again, 6GB/s is the theoretical limit of the hardware decompression block. Won't see that level of compression outside of edge caseOnly MSFT will try to get closer to the 6GB/s claim from Andrew Gossen.