How did Madman Ken Kutaragi, the lead designer of the ps3, filter so many with the CELL CPU?
>>106570205tech illiterate /v/ermin can't help themselves but to shit up /g/
advanced japanese engineering
It's like asking why every software can't be written in CUDA and with guaranteed performance improvements. The Cell is a GPGPU. If you want me to do it, you're gonna have to pay me above American minimum wage or some chinkjeetslop
Cell processor was designed as a CPU pretending to be a CPU. The problem was it tried to be both and was bad at being both of those things, while also being a concurrency nightmare, which for video games is essential. Taking max advantage of it would require a crazy amount of careful planning and a complete shift in game dev to figure out how to do it properly. The industry shifted to GPUs being more and more capable of more complex processing, similar to what the cell was supposed to be, but much better and still able to be paired with a good CPU. It was a bet for the future for Sony and they made the wrong bet. CUDA programming is functionally very similar to programming for the cell processor.
>>106570189It's time for you to log the fuck off cunt and stop shitting up this board
>>106570984>Japanese engineering>IBM Cell chiplol
When you actually learn how tech works you will realize that the xbox 360 was the better designed one >>106571080You meant to write as a gpu
>>106571528>You meant to write as a gpuI did, but unfortunately, I'm mentally retarded. It should be >Cell processor was designed as a GPU pretending to be a CPU
>>106571550I honestly don’t get it either, how on earth could a mid 00s cpu have been fast enough for drawing graphics?
>>106570189By failing to provide useful documentation.
>>106570189> oh boy! it's another spam read by the same resident sex offender that's always spammingkill yourselfhttps://desuarchive.org/g/search/image/cyDXMIPWRux1SOWyuVYlRg/
>it wasn't poorly engineered trash it uh-uh-uh-uh-uh-uh-uh-uh-uh fiturrd!Yeah, great insight there, moron.
>>106570189>21849312984th cell postWhy don't you shut the fuck up and get a life already?
>>106573408have you considered not spamming the board like that apple pedophile or are you the very same low iq street shitter pedo that everyone laughs at?https://desuarchive.org/g/search/image/PD-6Y1hXyU5BthJ9aLxpxg/
>>106574862If >>106570205 getting removed and then reinstated as >>106574756 isn't proof that he's a janny, then I don't know what is.
>>106574878it's confirmed. they are such massive fucking losers that is hilarious. they keep getting caught out. they even try to change image hashes and then realize:>oh yeah, i forgot i was fucking retarded and archives exist>and people have taken screenshotsabsolute losers. and they try banning people for exposing to the board just how massive these losers are. an anon here weeks ago claimed that one even tried reporting to desuarchive compilation pictures of their spamming as child pornography. they weren't deleted. lol.
>what if... we created a console... with a GPU and a GPU...
>>106577432Nigga….
>>106573408>It can only execute one instruction per clock cycle (at best).The PPE is dual-threaded and has dual-issuing, so it can, at best, execute four instructions per cycle.
>>106570189This idiot was only in it for benevolence at Sony, now he's gone.
We should throw OP into the bloodthirsty halls of the Famitsu sales thread.
>>106571652I'm a no coder so take it with a grain of salt, but they weren't cpus in the conventional sense. You can do cpu rendered ray tracing from what I've seen that's performant.They had specialized coprocessors that were good at specific workloads, vector based work here, instead of having a general processor that handles multiple things.You had a master processor and the coprocessors underneath it. Operations were local to their own cache for the coprocessors unless the master was used to do memory access to other regions and the master handles other more general CPU tasks. I'm not programmer, but I don't think game developers at the time were ready to write programs with heavy multi threading, or handling deep memory management. I don't think it had any caching system in the HW either for the coprocessor so you'd have to write something yourself as well.IDK why sony expected studios to be able to deal with such esoteric technology in a consumer space without giving the industry primers on it and training before the PS3 launched.
>>106579855>IDK why sony expected studios to be able to deal with such esoteric technology in a consumer space without giving the industry primers on it and training before the PS3 launched.The PS2.
>>106579855>>106579870 is righthttps://archive.arstechnica.com/reviews/1q00/playstation2/m-ee-1.htmlplug into internet archive to see the pics
>>106573408The PS3 cell had more compute power/speed than the PS4. Internet rando quoted is retard.
>>106579894Even better resourcehttps://www.copetti.org/writings/consoles/
>>106579894>>106579973Cool. I'll read these, thanks.
>filter so manydid it? the PS3 had a ton of software written for it.
>>106570189IBM really fucked Sony over. They hid many issues, and then secretly sold a sister design to MS after taking a check from Sony to develop the Cell.
>>106581137yep, they could've used a older power5 design for the ppe, but instead opted for some half-baked proto power6 as the basis for the PPE, and it really hurt it badly, likely was intended to run at 4ghz too , but the power consumption is too high on the 90nm process they initially used.
>>106581137>then secretly sold a sister design to MS after taking a check from Sony to develop the Cell.Sony shouldn't have agreed that IBM could use the arch in products to sell to other parties, then.
>>106578057It had a completely normal GPU. Its CPU had its own scheduler and you had to do branchless programming on it - much like on a GPU.
