The Sony PS3 thread (apparently *still* obnoxious!)

Inane baanter or words of wisdom - you decide...
Locked
User avatar
Firefox
Sheepie Whore
Sheepie Whore
Posts: 11412
Joined: Fri Apr 26, 2002 6:15 pm 0
Location: Sheffield

Post by Firefox »

Mr Sony wrote:... powered by a 64-bit superscalar RISC processor with six integrated 128-bit vector processors each with its own local RAM all running at 3.2GHz...
Game programmers wrote:Image
:?
"I am a very considerate person. If I want to go out all night on my miniature golf course and shoot lizards, well, no reason to keep the neighbours awake..."
User avatar
benedictw
Baaaaaaa!
Baaaaaaa!
Posts: 6012
Joined: Thu Mar 25, 2004 3:44 pm 0
XBL Gamertag: CoderBen
Location: Poole, UK
Contact:

Post by benedictw »

Firefox wrote:
Mr Sony wrote:... powered by a 64-bit superscalar RISC processor with six integrated 128-bit vector processors each with its own local RAM all running at 3.2GHz...
Game programmers wrote:Image
:?
Naw.

Image
Gamertag\PSN: CoderBen
User avatar
arron
Baaaaaaa!
Baaaaaaa!
Posts: 7047
Joined: Mon Apr 22, 2002 11:42 pm 0
Location: Here and Now

Post by arron »

silent_unicorn wrote:Doom has clever PC specific coding which needs to be recreated on each platform.
I was under the impression that the only 'clever' fast routines on Doom was being able to draw horizontal and vertical lines really quickly in assembler. You can learn how to do that by reading the "Graphic Programming Black Book" by Michael Abrash, which I found to be a good book to understand the "zen of assembly language". It's a free download, and well worth a read. He did have a hand in Quake, so I guess he knows what he's talking about.. :)

The rest of Doom was all written in C, which as I understood from my pitiful 15 years of Unix experience was developed to help port the kernel and software from one machine to another without making hardware specific changes. These days, abstraction libraries are even more common since the age of hardware accelleration, so it make more sense to use DirectX/OpenGL or a wrapper library make like a bit easier for yourself and then make that library work on all the machines you can.

This then leaves developers (programmers and artists) more time and effort doing creative stuff like writing the game..a much more productive use of their time..
"Observation is the path to understanding. Self-observation is the path to self-understanding."
User avatar
Flabio
Baaaaaaa!
Baaaaaaa!
Posts: 8717
Joined: Wed Mar 03, 2004 12:37 pm 0
Location: Guildford

Post by Flabio »

Ay, in a big 360 or PS3 game only around 40% of the code base is going to be platform specific. Of course, getting that 40% to work efficiently on two radically different platforms can be fun. Not to mention that you might have to reauthor art and level assets to fit the engines.

But yeah, the work I do, I could be coding on the Dreamcast for all the difference it makes...
User avatar
Rod_S
Sheepie Whore
Sheepie Whore
Posts: 13474
Joined: Thu Jan 23, 2003 10:18 pm 0
Location: Badsville
Contact:

Post by Rod_S »

Flabio wrote: But yeah, the work I do, I could be coding on the Dreamcast for all the difference it makes...
I look forward to Spong's "Lionhead Dreamcast EXCLUSIVE" headline :D
User avatar
merman
Sheepie Whore
Sheepie Whore
Posts: 10943
Joined: Wed Feb 16, 2005 1:44 pm 0
XBL Gamertag: merman1974
Yahoo Messenger: andrewrfisher
Location: Skegness, England
Contact:

Post by merman »

Flabio wrote:Ay, in a big 360 or PS3 game only around 40% of the code base is going to be platform specific. Of course, getting that 40% to work efficiently on two radically different platforms can be fun. Not to mention that you might have to reauthor art and level assets to fit the engines.

But yeah, the work I do, I could be coding on the Dreamcast for all the difference it makes...
Or you can use middleware like the Unreal 3 Engine...
Twitter, Xbox, Wii U and Steam - merman1974
ZZAP is back - https://www.patreon.com/zzapmagazine
User avatar
arron
Baaaaaaa!
Baaaaaaa!
Posts: 7047
Joined: Mon Apr 22, 2002 11:42 pm 0
Location: Here and Now

Post by arron »

Well, as the unsurpassable Shawn Hargreaves once told me - you might as well write the whole lot in unoptimised code, and then work out where the bottlenecks are, and then spend 90% of your optimising time making the critical 10% of the code to run faster, for the best performance improvement. In some cases, performance loss isn't even your fault, at least as far as your code is concerned.

He showed me once where a microcode library update on the N64 devkit resulted in a 40% increase in code speed in certain critical routines for no extra work. It goes to show that a small effort can reap the largest dividend in speed improvement..

I myself used a x86_64 Intel Fortran compiler on MCNPX source to get a 3x performance increase over the third party Portland product that the original developers were using..well, I was impressed!

As for complicated architectures..unless you're building your application to take advantage of the optimisation in hardware then you're wasting your time anyway. And if your dev setup gives OK results given suboptimal code, then I doubt people are going to spend weeks making it run better.

A PS3 would run most of my work much slower than a PC because it relies on huge data arrays and repeated double precision floating point calculations. A PS3 is much better at dealing with streams of data and repeated calculations that don't change other calculations already in progress elsewhere in the application. There's no real way that even if I coded the whole application in assembly it would make the application work any better on a PS3. It's just a complete dog for the intended application..

Some things are not designed to work that well together. Like a steam engine powered plane. Or baked beans in curry. It's just how things are..
"Observation is the path to understanding. Self-observation is the path to self-understanding."
User avatar
Kamineko
Baaaaaaa!
Baaaaaaa!
Posts: 7569
Joined: Fri Dec 17, 2004 2:53 pm 0
Contact:

Post by Kamineko »

Rod_S wrote:
Flabio wrote: But yeah, the work I do, I could be coding on the Dreamcast for all the difference it makes...
I look forward to Spong's "Lionhead Dreamcast EXCLUSIVE" headline :D
Whatever happened to Black and White for the Dreamcast anyways?
your dev setup gives OK results given suboptimal code
You've just summed up everything I've ever done.
User avatar
Bubba
Sheepie Whore
Sheepie Whore
Posts: 10013
Joined: Tue Apr 22, 2003 12:52 pm 0
XBL Gamertag: BubbaFatAss
PSN: BubbaFatAs
Location: Cambridge

Post by Bubba »

arron wrote:I myself used a x86_64 Intel Fortran compiler on MCNPX source to get a 3x performance increase over the third party Portland product that the original developers were using..well, I was impressed!
Intel make lovely compilers :D Closely followed by MS and IBM. I wonder what the Sony cell compiler is like in comparison to the IBM one?

Cheers

Bubba
||Work || Flickr||
User avatar
Kemper_Boyd
Sheepie Whore
Sheepie Whore
Posts: 11967
Joined: Wed Jul 31, 2002 9:15 pm 0

Post by Kemper_Boyd »

Arron I'm not sure you are right about your assessment of Cell
if MCNPX is the sort of thing you run. LANL are building a Cell-based
supercomputer called Road Runner. 3d radiation transport codes
are one of the applications they are going to run, and they've
reported significant speed-ups for hybrid applications compared
to Opteron only systems.
User avatar
arron
Baaaaaaa!
Baaaaaaa!
Posts: 7047
Joined: Mon Apr 22, 2002 11:42 pm 0
Location: Here and Now

Post by arron »

Kemper_Boyd wrote:Arron I'm not sure you are right about your assessment of Cell
if MCNPX is the sort of thing you run. LANL are building a Cell-based
supercomputer called Road Runner. 3d radiation transport codes
are one of the applications they are going to run, and they've
reported significant speed-ups for hybrid applications compared
to Opteron only systems.
Depends on the models they are using and how they are implemented. It also depends on the hardware. As I understand it, the Cell processor is not disimilar to the Cray approach to aupercomputing. Back then they used subprocessors to overcome the bandwidth and latency issues getting data into the main processors. If you put a shedload of memory into it, and wire it up properly on the hardware, and write the software the right way with decent optimisation tools then I imagine you can get some impressive results. Stock PS3s are not supercomputers and aren't designed for that type of computing. The point I was trying to make that a modern hardware spec is no guarantee that it will be good for doing intensive computing on if you don't know what you're doing..:)

Compared to a standard PC, the PS3 is a pretty poor general computing device with limited memory for applications. The Cell processor used in the PS3 has a substantial performance hit using double precision, so it wouldn't be good for my applications :)
"Observation is the path to understanding. Self-observation is the path to self-understanding."
User avatar
pogo
Sheepie Whore
Sheepie Whore
Posts: 14180
Joined: Tue Sep 10, 2002 8:28 pm 0
Yahoo Messenger: BrassSparrow
Location: County Durham

Post by pogo »

arron wrote:Compared to a standard PC, the PS3 is a pretty poor general computing device with limited memory for applications. The Cell processor used in the PS3 has a substantial performance hit using double precision, so it wouldn't be good for my applications :)
I'd say it's the other way around - the PS3 is a much better general purpose platform than the PC. You can on the same platform run 32 bit code, 64 bit code, vector code and code (scalar or vector) on up to 7 separate processing units.

On a PC only the first is guaranteed. You can assume some level of vector support, but you'll want to check which version of SSE first. 64 bit is out of the question on 95% of PCs, as is assuming more than one core (even if it has 2 or more there's no guarantee you'll be able to use them all to 100%).

Double precision is a very specialised rather than general use, but even that is much faster on the PS3, at least for scalar code. But the PS3's real strength is parallel code, useful e.g. in the rendering pipeline, a multi-body dynamics system, a large AI system or sound processing.

As for RAM, that's needed on a PC as you don't know whether the user has a full, fragmented IDE drive for data, or a RAID array of new SATA drives, or what speed their CD/DVD drive is, or what other programs such as for e-mail or torrents is also running. You have to load everything into RAM to avoid stalls, on top of whatever the OS needs. On a PS3 when your app is running you have exclusive access to a fast optical drive and HD, both with known performance characteristics, so can stream.

But most important : you don't need to build in RAM and performance overheads to allow for vastly different configurations, drivers and OS versions. You just code it to run as fast as you want on the standard PS3 (or 360).

Remember the PS2 or Xbox? Limited in similar ways, except 10x more so. But this didn't stop developers making games like Halo, GTA, FFXII, Ico, MGS2, etc., much better than similar games on the PC.
User avatar
Dio
Sheepie Whore
Sheepie Whore
Posts: 18887
Joined: Mon May 31, 2004 1:08 pm 0
Location: Newcastle UK

Post by Dio »

You need to separate discussion of the core (Cell) from the console (PS3). That was an interleaved and somewhat confused mess.

x86 is an incredible general-purpose platform - the hugely-optimised OOE cores are fast on any code you care to throw at it. I'd have thought something like Cell would need a lot of work on specific algorithms to outperform it - but that said, it should be a better HPC platform.

For games, a £600 PC built now could absolutely murderise any console platform, if it was programmed to its full ability. Of course, that doesn't happen, and that's also far more expensive even than a PS3.
Last edited by Dio on Mon Oct 01, 2007 9:47 pm 0, edited 1 time in total.
User avatar
Kemper_Boyd
Sheepie Whore
Sheepie Whore
Posts: 11967
Joined: Wed Jul 31, 2002 9:15 pm 0

Post by Kemper_Boyd »

arron wrote:If you put a shedload of memory into it, and wire it up properly on the hardware, and write the software the right way with decent optimisation tools then I imagine you can get some impressive results. Stock PS3s are not supercomputers and aren't designed for that type of computing. The point I was trying to make that a modern hardware spec is no guarantee that it will be good for doing intensive computing on if you don't know what you're doing..:)
I don't see what point you are making. What you've said is true of any
system. Even the suggestion that it's not designed for supercomputing
has little relevance when most of the largest supercomputers use off
the shelf parts.
arron wrote:Compared to a standard PC, the PS3 is a pretty poor general computing device with limited memory for applications. The Cell processor used in the PS3 has a substantial performance hit using double precision, so it wouldn't be good for my applications :)
It's true that the SPEs don't have fully pipelined double precision FPUs,
even with that being the case Cell still beats a lot of its contemporaries
and by wide margins in many cases.
User avatar
arron
Baaaaaaa!
Baaaaaaa!
Posts: 7047
Joined: Mon Apr 22, 2002 11:42 pm 0
Location: Here and Now

Post by arron »

pogo wrote:[As for RAM, that's needed on a PC as you don't know whether the user has a full, fragmented IDE drive for data, or a RAID array of new SATA drives, or what speed their CD/DVD drive is, or what other programs such as for e-mail or torrents is also running. You have to load everything into RAM to avoid stalls, on top of whatever the OS needs. On a PS3 when your app is running you have exclusive access to a fast optical drive and HD, both with known performance characteristics, so can stream.

But most important : you don't need to build in RAM and performance overheads to allow for vastly different configurations, drivers and OS versions. You just code it to run as fast as you want on the standard PS3 (or 360).

Remember the PS2 or Xbox? Limited in similar ways, except 10x more so. But this didn't stop developers making games like Halo, GTA, FFXII, Ico, MGS2, etc., much better than similar games on the PC.
The console does what it was designed to do (graphics and games applications), but given that my models use approximately 2.5 GB per problem instance in data, it all has to be resident as the contents can change with each 'computational event' and whilst several different stocastic physical models running simultaneously altering the data as you go. It's not like I can squirt the lot through a vector processor to solve a lot of matrix calculations. It's mostly random number generation and using that through a markov chain monte carlo process - something a console does very little of.

You can't stream the data off some kind of device (or use swap space) as soon as you do that then you're using device access many times slower than memory access..so the streaming capabilities of the PS3 are pretty useless for what I do.

As I said, you can engineer the cell into HPC servers to attack certain types of problems effectively if you build the system right in the first place with the right support hardware and software to go with it. Console hardware does what it does well (providing it is programmed right by someone with a clue) but it is targeted towards a certain type of application (games), and it will do badly at others. PC hardware is designed to be much more multipurpose which is why so much of it is upgradable. Horses for courses innit?
Last edited by arron on Mon Oct 01, 2007 11:15 pm 0, edited 1 time in total.
"Observation is the path to understanding. Self-observation is the path to self-understanding."
Locked