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:
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:
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..silent_unicorn wrote:Doom has clever PC specific coding which needs to be recreated on each platform.

Or you can use middleware like the Unreal 3 Engine...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...
Whatever happened to Black and White for the Dreamcast anyways?Rod_S wrote:I look forward to Spong's "Lionhead Dreamcast EXCLUSIVE" headlineFlabio wrote: But yeah, the work I do, I could be coding on the Dreamcast for all the difference it makes...
You've just summed up everything I've ever done.your dev setup gives OK results given suboptimal code

Intel make lovely compilersarron 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!

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..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.

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.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 don't see what point you are making. What you've said is true of anyarron 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..
It's true that the SPEs don't have fully pipelined double precision FPUs,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
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.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.