Joined: 22 Sep 2005Posts: 1392Location: In your imagination......yup, you are having visions of me.

Posted: Tue Nov 08, 2005 9:06 pm Post subject:

sabotage wrote:

Which way would be more benficial though? Having each core work on something specific or spreading everything out?

Having each core work on specifics. That reduces bottlenecks by.............a heck of alot.

Imagine it. If you have one core devoted itself entirely to AI, only AI code will run through that PPU. Bottlenecks can happen because of the system ( each core has two threads so developers have to split their code) but they will mainly happen because of poor coding.

Now if you have one core working on both AI and structural physics, (Body) the two lines might mesh, and since now you are dealing with two threads that interlace, it will take sometime to figure WHY.

Although i suppose just throwing everything in there w/o specifics might be easier to program.

ninja of choas, u seems to know alot about this consoul much as i do. not just that but the code of conversion to blue-ray format is also very difficult to do. changing the light spectum from red to blue is not easy. i myself will be a future game designer soon._________________

Having each core work on specifics. That reduces bottlenecks by.............a heck of alot.

Imagine it. If you have one core devoted itself entirely to AI, only AI code will run through that PPU. Bottlenecks can happen because of the system ( each core has two threads so developers have to split their code) but they will mainly happen because of poor coding.

Now if you have one core working on both AI and structural physics, (Body) the two lines might mesh, and since now you are dealing with two threads that interlace, it will take sometime to figure WHY.

Although i suppose just throwing everything in there w/o specifics might be easier to program.