at this point, I'm inclined to believe him. We will find out in april.
From all that I have read not even the insiders and devs knows exactly what's going on with durango. I doubt the nextbox specs will look anything like the vgleaks posts.
That's a good question, I've always assumed them to be just rewordings of the official documents, but that could be completely wrong.But at the same time - are these actual dev-docs or just VGleaks essays?
This is probably true from a game development PoV actually. If you have a HPC background you'll be thinking about the precision of the intermediate results, but I don't think that would matter in games.Is that really an improvement? They state separate MUL/ADD execution resources, ultimately I don't care if I issue a MADD or MUL+ADD if they both execute in 1 cycle on average (not to mention much of MADDs usage is interchangeable with DOT).
That's a good question, I've always assumed them to be just rewordings of the official documents, but that could be completely wrong.
If they want to launch this year they will not have changed majorly.
Consoles take time, revisions take time.
Well, there you have your reason. Image processing (well, most image processing) is one of the most latency-invariant workloads out there. There are others that would be impacted a lot more.Isn't fetching data from main gddr5 like a 200~300 cycle penalty for a wavefront if remember it right?
But you can easily mask this penalty by having enough wavefronts running doing calculations.
You can probably increase efficiency for a lot of algorithms if that initial penalty can be brought down to 50~100 cycle penalty.
Because most the time when i used opencl for image processing i was memory bound read pixel in write pixel out..
even though nothing is official, this is what makes the most sense.
MS may have chosen to build a candy box, and fill it with crack (apps, microtransactions, lower retail priced gamesdue to no resales etc...).
Since the box is a diversion, they may have focused on making it very small (wife acceptance factor), very cheap (to get people have several candy boxes at home) etc...
And for most people, 720 vs 360 graphics will be mind blowing anyway.
MS is doing to consoles what dealers do to drugs. Build reputation, work on your customers addiction, and then dilute your drugs and keep selling them at the same price.
Don't really think his trolling,but yeah very wiredRead KidBeta's post. It is far more likely he was trolling.
256Gb/s = 32GB/s, 106GB/s = 106GB/s
Gb/8 = GB
Sony changed their specs last summer, then again a few months ago adding 4 more gigabytes, MS changed specs right before 360 released. It is not impossible for MS to change the specs of Durango within a year and half.
Sony added more RAM, that is different to completely redesigning everything to incorporate a new CPU and GPU.
RAM increase is doable.
Sony added more RAM, that is different to completely redesigning everything to incorporate a new CPU and GPU.
RAM increase is doable.
Sony changed their specs last summer, then again a few months ago adding 4 more gigabytes, MS changed specs right before 360 released. It is not impossible for MS to change the specs of Durango within a year and half.
Isn't Sony rumored to be tweaking CPU clock speeds?
WHAT? Even the Wii (and of course Espresso) or the Xenon CPU cores had cache locking!! This is a very useful feature performance-wise that helps a when you want to squeeze the CPU close to its theoretical limits and save a good amount of bandwidth.Looks really standard.The Durango CPU does not support line or way locking in either L1 or L2, and has no L3 cache.
This was one of the rumored modifications. Doesn't look like it's happening.
No FMA either, I thought that might happen after the improved vector units rumor.
Hope springs eternal
Last Summer they upgraded the specs, not just the ram.
Isn't Sony rumored to be tweaking CPU clock speeds?
Pretty sure that the eDRAM had 32GB/s from the main GPU die and had 256GB/s between the eDRAM and the ROPs (that are on the same die).
http://www.beyond3d.com/content/articles/4/3
http://fileadmin.cs.lth.se/cs/Personal/Michael_Doggett/talks/eg05-xenos-doggett.pdf
This would be the first time in history MS kept a console's specs completely static for an entire year. Would be hilarious if really true.
Somebody call bgassassin.
Exactly, 256GB/s in 360 edram are for the ROPs.
So in Durango, are the 106GB/s between the GPU die and ESRAM? where are the ROPS in this scheme?
Sony appear to have done the same - barring the RAM increase
Yet more lies from 'insiders'. Will it ever end?
You guys are brave. I'm not going to call anyone out until I get final specs, lol.
Bandwidth on GDDR5 was changed.
You guys are brave. I'm not going to call anyone out until I get final specs, lol.
Isn't Sony rumored to be tweaking CPU clock speeds?
This would be the first time in history MS kept a console's specs completely static for an entire year. Would be hilarious if really true.
Nope. Core specs have stayed the same for Sony. Look how far back the rumours go. The only real surprise was the RAM. The PS4 was expected to have a Jaguar processor. The PS4 was also expected to have a 7xxx variant.Sony changed their specs last summer, then again a few months ago adding 4 more gigabytes, MS changed specs right before 360 released. It is not impossible for MS to change the specs of Durango within a year and half.
Wouldn't that indicate that they have got a solid road plan and are sticking to it? Last minute changes often indicate a lack of foresight...
In the case of PS4, changes to the roadplan don't seem major at all, just an upgrade of ram, which doesnt seem to have been technically difficult to pull of. Also, from what Sony have been saying, developing PS4 has been an iterative approach.
Who knows what is the case with Durango though...there was a lot of initial info then little since.
Nope. Core specs have stayed the same for Sony. Look how far back the rumours go. The only real surprise was the RAM. The PS4 was expected to have a Jaguar processor. The PS4 was also expected to have a 7xxx variant.
There was supposed to be no info. SuperDaE exploited encrypted documents from Microsoft's server.
Bandwidth on GDDR5 was changed.
Bandwidth on GDDR5 was changed.
BruceLeeRoy gave us the current number.
That was to take advantage of lower power GDDR5, 1.35v vs 1.55v per chip. It represents a significant power saving over 16 chips and makes cooling much simpler/cheaper also. Losing that 16GB/s worth of bandwidth was probably seen as worth it for the cooling and TDP gain.
Yeah decreased.
Don't forget the beta dev kits with the final GPU / Memory / DME's / (2 display planes) went out about a month ago. This stuff is shipping already its not up in the air anymore.
If the Durango CPU is really like this then I have to say that this is rather weak engineering. Separate L2s with no L3? No common cache for CPU and GPU? They're not using any benefits of APU if that info is true. I wonder why go with an APU at all in that case...
So it's just standard Jaguar? No special sauce?
Where is your Gies now?
Good point. Generally, it's just RAM and clocks likely still malleable.
I think people say there aren't DDR3 chips to allow MS to double RAM. But, they said the same thing about GDDR5 right before Sony did it, so I dont put much stock in it.
It would be pretty crazy lopsided to pair the equivalent of a 7770 with 16GB of RAM though. Hell, 8GB and the 7850 in PS4 is already kinda ram unbalanced imo. Even allowing the RAM must serve the whole system and not just the GPU.
So it's just standard Jaguar? No special sauce?
Where is your Gies now?
Well, that's disappointing to know that consoles are not a match for 2012 PC hardware. :/