PS3 GPU not fast enough.. yet?

Though I agree wholeheartedly from a game perspective, what about non-gaming functions? This data suggests PS3 has 256 MB for 'Linux' work. For photo or video editing, working in the GDDR isn't an option it seems, and that RAM will be all but redundant for such tasks ???. Which wouldn't be surprising, as these extra applications are something of an afterthought I think, rather than the machine being purposefully designed for them.

Also I still don't get where the 16 MB connection is coming from. Did they just solder a bit of copper wire from pin to pin?! How is that handled over the existing Buses? A tiddly little share of the command processor on RSX? Wouldn't a shared memory channel be 4 GB/s up and down shared, rather than 4 GB down, 0.016 GB up?

 

It is true, I think it all comes down to my childhood and how my growing up influenced my relations with others and especially girls... wait a moment maybe I ... am... uhm... I misunderstood something... *whistles away*

So you think that XDR was chosen instead of a lower bandwidth solution with in mind the need of helping RSX not to be bandwidth starved with its lone 22.4 GB/s link to its VRAM ?

Truth to be told, according to that slide, XDR and its XMC seem to be MUCH more efficient at reaching peak bandwidth when the CBE chip is writing to it rather than reading from it:

XDR Reads initiated by the CBE chip: 16.8 GB/s of 25.6 GB/s ~= 65.625%

XDR Writes initiated by the CBE chip: 24.9 GB/s of 25.6 GB/s ~= 97.27%

It seems that writing to XDR from CELL being so MUCH more efficient than reading from it would favor a LOT the idea of writing to XDR from CELL and initiating a read from RSX rather than writing from CELL over to RSX's GDDR3 memory.

P.S.: Please digress more and more often, I do not think people mind it at all .

 

I don't think its something physical, I'm beginning to suspect that this is an overall processing rate. If Cell is requesting something from RSX's memory then it may need to go in as a command and be queued, ready for RSX to retrieve and pass out when it can schedule the work.

[Edit] Note the "~" on the Cell read/writes.

 

need writeback tilecaches

 

according to EXIF data the picture was taken the 4th of June, 20:20:59

 

Your PI skills are weak.. it seems likely that Sony don't hold DevStation events at 8:20pm on a Sunday night..



Dean

 

Yes, following Dean's comments, isn't that more likely the time the image was posted/received, seeing as that was yesterday? Unless there was a second DevStation event that we haven't heard about...

 

the purpose of exif data is to store in the jpeg some data about the shot like the aperture, the camera model, iso and time the picture was taken.

 

sorry, nm.

 

I just said what indication gives the EXIF data.. it's a fact

That must be taken with a grain of salt as you can set this value at the value you want by setting the time of the camero or manipulating EXIF headers

And even if this value is true we don't know the timezone, maybe Charlie Demerjian took it (his place of residence would be a clue), maybe someone else..

Why do you think it was taken during a devstation event ? AFAIK it could be a shot of a PDF on some TFT screen, during a flight to Japan..

 

Actually, good point. Just because it says DevStation, doesn't mean that's when it was being shown for this photo.

 

EXIF data is actually quite easy to change.

Just ask google.

Slate.com did an article about it a couple of months ago http://www.slate.com/id/2140303/ where EXIF data from a picture was used in a courtcase.

 

one thing from this article: the ps3 is my dream pc. monstrous bandwidths in all the right directions.

sans the tri setup - that's a bummer.

 

Okay now this story is really getting interesting.

 

Yeah.. makes sense. Sorry 'bout that, Magnum.

Dean

 

That's why he's the PI and we're not

 

Yeah.. I should learn to never doubt the power of a dodgy moustache..

Dean

 

So is this info true or false? I myself, never trust the inquire, since they've been wrong many times in the past

 

It's true, but mostly irrelevent. Which is to say... ignore the entirety of Charlie D's article text, look simply at the slide, and contemplate the implications. There really aren't many.

 

The only real implication is that non-graphics data and graphics data processed on CELL has to be stored in 256MB.

Shock, shock and horror. It's all over.
We're all gonna die tommorow!
... What? Oh, alright, nm then.


Uttar