Sony Technical Information on PS3


Recommended Posts

http://www.watch.impress.co.jp/game/docs/20060329/3dps3.htm

* PPE has 128 VMX registers

* Memory Latency to cell:

1) Register: 1 Cycle

2) L1 Cache : 8 Cycles

3) L2 Cache : 32 Cycles

4) Main memory: 140 Cycles

* Overall Cycles: 500, same as Xbox 360

* 6 SPEs reserved for games, 1 SPE reserved for Operating System

* RSX is based on N47 Nvidia Architecture = Nvidia 7800 GTX

* RSX is 384 Flops per Clock at @550 Mhz, Nvidia 7800 GTX is 728 Flops per Clock @430 Mhz

* SPEs cannot access main memory directly

2)

Link to comment
https://www.neowin.net/forum/topic/447554-sony-technical-information-on-ps3/
Share on other sites

* Memory Latency to cell:

1) Register: 1 Cycle

2) L1 Cache : 8 Cycles

3) L2 Cache : 32 Cycles

4) Main memory: 140 Cycles

* Overall Cycles: 500, same as Xbox 360

Not overall cycles. Xbox 360 main memory have 500+ cycles latency, with latency lower is better.

Anyway most of this is already know before.

Sony upgraded the VMX registers on the PPE from 64 to 128

I thought RSX was just a G70 @ 128bit, if that is true its a downgrade from what I assumed it to be.

it shouldnt have been a surprise. GTX has more memory bandwidth than RSX. even X1900 has more memory bandwidth than the Xenos in Xbox 360

it shouldnt have been a surprise. GTX has more memory bandwidth than RSX. even X1900 has more memory bandwidth than the Xenos in Xbox 360

No, my point was that I expected RSX to turn out the same number of flops per clock as a regular G70 but it would have less memory bandwidth (128bit).

According to your specs, you have the the RSX at lower flop per clock performance. <- Where did you get that figure btw? :huh:

No, my point was that I expected RSX to turn out the same number of flops per clock as a regular G70 but it would have less memory bandwidth (128bit).

According to your specs, you have the the RSX at lower flop per clock performance. <- Where did you get that figure btw? :huh:

RSX

http://www.watch.impress.co.jp/game/docs/2...329/3dps309.jpg

G70(7800 GTX)

http://www.pcperspective.com/images/review.../g70summary.jpg

personally I dont think it really matters, does it? I mean if the programmers can take full utilization from the cell, couldn't they really just render most of the stuff needed on the processor subtract textures-fillings-etc? If so this would take the load off of the gpu, and allowing the gpu to do all textures-hdr-bumpmapping-etc..?

So if the cell only has 6 usable SPEs and it's supposed to do some graphics, all those kick-ass physics and whatnot -- whats going to run the gamecode? :blink:

People have to realise that the Cell isn't some super processor (outside of the usual marketing speak ofcourse). There has to be balance somewhere. It may be able to do alot of things but surely it can't do them all at once and do them well :rolleyes:

So if the cell only has 6 usable SPEs and it's supposed to do some graphics, all those kick-ass physics and whatnot -- whats going to run the gamecode? :blink:

People have to realise that the Cell isn't some super processor (outside of the usual marketing speak ofcourse). There has to be balance somewhere. It may be able to do alot of things but surely it can't do them all at once and do them well :rolleyes:

The RSX takes care of the graphics the Cell does everything else as far as i know.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • YES!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    • Apple are scared of their customers! They have built a brand over the years of "it just works out of the box", but that slows innovation. Samsung's master stroke was the Galaxy Ultra: "Let's cram everything into one handset, make it so stupid only real nerds will love it, some of the features will work, some won't, but the audience will have such a high tolerance they won't care". Apple has no such device and so they are constantly worrying these days about the fallout of creating a new experience that customers might not like. I know it is often cited the reason they don't build a touchscreen Mac Book is they don't want to cannibalise the the iPad market, but I think it's equally cold feet after the criticism Microsoft receive trying to make a touch compatible desktop OS
    • HandBrake 1.11.2 by Razvan Serea HandBrake is an open-source, GPL-licensed, multiplatform, multithreaded video transcoder, available for MacOS X, Linux and Windows. Handbrake can process most common multimedia files and any DVD or BluRay sources that do not contain any kind of copy protection. Here is a detailed breakdown of HandBrake’s features: Built-in Device Presets—Get started with HandBrake in seconds by choosing a profile optimized for your device, or choose a universal profile for standard or high quality conversions. Simple, easy, fast. For those that want more choice, tweak many basic and advanced options to improve your encodes. Supported Input Sources—Handbrake can process most common multimedia files and any DVD or Blu-ray sources that do not contain any kind of copy protection. Outputs: File Containers: .MP4(.M4V) and .MKV Video Encoders: H.265 (x265 and QuickSync), H.264(x264 and QuickSync), H.265 MPEG-4 and MPEG-2, VP8 and Theora Audio Encoders: AAC / HE-AAC, MP3, Flac, AC3, or Vorbis Audio Pass-thru: AC-3, E-AC3, DTS, DTS-HD, TrueHD, AAC and MP3 tracks Additional features: Title/ Chapter Selection Queue up Multiple Encodes Chapter Markers Subtitles (VobSub, Closed Captions CEA-608, SSA, SRT) Constant Quality or Average BitRate Video Encoding Support for VFR, CFR and VFR Video Filters—Deinterlacing, Decomb, Detelecine, Deblock, Grayscale, Cropping and Scaling Live Video Preview HandBrake 1.11.2 changelog: All platforms Video Fixed a crash that happened when doing a 2-pass lossless x265 encode Fixed a memory leak that happened when doing a 2-pass MPEG-4/MPEG-2/VP9/FFV1 encode Audio Updated the list of supported dithers and encoders combinations Fixed the Core Audio AAC encoder 7.1 channel layout Subtitles Fixed the VobSub palette creation in the MP4 container Build system Improved build system compatibility with older build tools Third-party libraries FFmpeg 8.0.2 (decoding and filters) SVT-AV1 4.1.0 (AV1 video encoding) Linux Added WebM MIME type to the list of the supported formats Mac Improved handling of unsupported presets Updated Sparkle automatic update library Windows Improved handling of unsupported presets Improved queue low space pause behaviour Fixed the automatic audio track name generation Fixed the summary description of HDR video Download: HandBrake 64-bit | Portable 64-bit | ~30.0 (Open Source) Download: HandBrake ARM64 | Portable Links: HandBrake Website | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • So, an article that has nothing to do with Windows 11, still gets Windows 11 in the title and a build number as the picture? Dell have a buggy build of Support Assist HP have UEFI settings that need unlocking for the secureboot cert upgrade to take place.
    • What I can't seem to understand is that Google are paying SpaceX? Surely it would be the other way round, with SpaceX needing Google's datacenters etc.? Oh well, this level of money and power is way outside of my comprehension at the best of times.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Steven P.
      71
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      67
  • Tell a friend

    Love Neowin? Tell a friend!