I would normally host the picture but imageshack is being incredibly lame so I thought I'd cut the crap and give you the whole page

Real or Fake? DXAlpha decides!
Just checked the rest of the page

Moderator: Forum Guards
No arse kissing involved here! You can download 2 other episodes from the marketplace, and not just lame little clothing packs or two new cars like on Saints Row we're talking a whole other fudging island!C:Enter:£££ wrote:Probably arse kissing but I can't fucking wait for this shit! Bring on October!
C:Enter:£££ wrote:No, GTA4. London, London Expansion, Vice City, VC Stories, LC Stories and SA are side games. Each #GTA has had a new engine.
Mandalore wrote:It'd be best on pc.Mainly as the XBox 360 doesn't have a GTX 8800.
Oh sweet imagine that! All these pixels kicking eachother's arses. Speaking of GTA 2 do you think it might be available from marketplace once GTA 4 is released?C:Enter:£££ wrote:Man download GTA2, MP would be so good on it lol
C:Enter:£££ wrote:Shit happens when only 1 person can do it.
DarkKnight wrote:C:Enter:£££ wrote:Shit happens when only 1 person can do it.
Wow, what an insightfully stupid post.
Psykorgasm wrote:Makes sense.
The PPE is a 64-bit processor with a PowerPC instruction set, 64 KB of L1 cache memory, and 512K L2. Like Intel's HyperThreading, it supports simultaneous multithreading, but is remarkably simpler than Pentiums or Opterons.
SPEs are different. They have 128-bit registers and SIMD (single instruction, multiple data) instructions that can simultaneously process the four 32-bit words inside each register. Plus, there are so many registers (128) that you can unroll loops many times before running out of them. This is ideal for dataflow-based applications.
But the most radical peculiarity for programmers is that SPEs have no cache memory. Rather, they have a 256-KB-scratchpad memory called "local store" (LS). This makes SPEs small and efficient because caches cost silicon area and electrical power. Still, it complicates things for programmers. All the variables you declare are allocated in the LS and must fit there. Larger data structures in main memory can be accessed one block at a time; it is your responsibility to load/store blocks from/to main memory via explicit DMA transfers. You have to design your algorithms to operate on a small block of data at a time, fitting in the LS. When they are finished with a block, they commit the results to main memory, and fetch the next block. In a way, this feels like the old DOS days, when everything had to fit in the (in)famous 640 KB. On the other hand, an SPE's local storage (256 KB) is so much larger than most L1 data caches (a Xeon has just 32 KB). This is one of the reasons why a single SPE outperforms the highest-clocked Pentium Xeon core by a factor of three on many benchmarks.
Thanks to nine processors on a single silicon die, the Cell Broadband Engine—a processor jointly designed by IBM, Sony, and Toshiba and used in the PlayStation 3—promises lots of power. The good news is that the Cell is really fast: It provides enough computational power to replace a small high-performance cluster. The bad news is that it's difficult to program: Software that exploits the Cell's potential requires a development effort significantly greater than traditional platforms. If you expect to port your application efficiently to the Cell via recompilation or threads, think again.
In this article, we present strategies we've used to make a Breadth-First Search on graphs as fast as possible on the Cell, reaching a performance that's 22 times higher than Intel's Woodcrest, comparable to a 256-processor BlueGene/L supercomputer—and all this with just with a single Cell processor! Some techniques (loop unrolling, function inlining, SIMDization) are familiar; others (bulk synchronous parallelization, DMA traffic scheduling, overlapping of computation and transfers) are less so.
C:Enter:£££ wrote:Shit happens when only 1 person can do it.
C:Enter:£££ wrote:Yeh, the one that is really expensive to program for.
±MC Chedda'± wrote:Almost impossible aswell. All this for "realtime weapon change?!" and "giant enemy crabs from Japanese history".