I haven’t really pushed the device to its limits yet. But the best set of numbers I’ve seen are here:
http://glbenchmark.com/phonedetails.jsp?D=Apple%20iPhone

The general guideline is that the iPhone is going to be fill limited. For example, two full screen textured quads would probably drop framerate by a ton.

Memory management is also a sticky point. It’s the one thing that developers get caught on. Objective-C supports memory pools much in the way we allocated memory on the PSP.

You probably want per-game, per-frame, and per-event memory pools. (Objective-C with Cocoa is event driven)

I haven’t been able to get solid numbers on resources. The iPhone is much like a PC in this respect. And iPhone OS 2.1 actually improved memory management by a ton. So all those numbers would have to be recalculated.

The next time I run the Shark Profiler, I’ll dig up some numbers and post them.

I haven’t really pushed the device to its limits yet. But the best set of numbers I’ve seen are here:
http://glbenchmark.com/phonedetails.jsp?D=Apple%20iPhone

The general guideline is that the iPhone is going to be fill limited. For example, two full screen textured quads would probably drop framerate by a ton.

Memory management is also a sticky point. It’s the one thing that developers get caught on. Objective-C supports memory pools much in the way we allocated memory on the PSP.

You probably want per-game, per-frame, and per-event memory pools. (Objective-C with Cocoa is event driven)

I haven’t been able to get solid numbers on resources. The iPhone is much like a PC in this respect. And iPhone OS 2.1 actually improved memory management by a ton. So all those numbers would have to be recalculated.

The next time I run the Shark Profiler, I’ll dig up some numbers and post them.

I haven’t really pushed the device to its limits yet. But the best set of numbers I’ve seen are here:
http://glbenchmark.com/phonedetails.jsp?D=Apple%20iPhone

The general guideline is that the iPhone is going to be fill limited. For example, two full screen textured quads would probably drop framerate by a ton.

Memory management is also a sticky point. It’s the one thing that developers get caught on. Objective-C supports memory pools much in the way we allocated memory on the PSP.

You probably want per-game, per-frame, and per-event memory pools. (Objective-C with Cocoa is event driven)

I haven’t been able to get solid numbers on resources. The iPhone is much like a PC in this respect. And iPhone OS 2.1 actually improved memory management by a ton. So all those numbers would have to be recalculated.

The next time I run the Shark Profiler, I’ll dig up some numbers and post them.

Congrats on the new venture man – good stuff!

Have you done any metrics yet on rendering performance using OpenGL ES on the iPhone Hardware? I am wondering about things like polygon/texture budget needed to maintain 30Hz.

Also in the docs, it says that no more than 24MB of RAM should be allocated to texture and geometry. Do you know how much RAM is left for executable code at that point?

Likewise for sound – if you’re using 24MB for visuals, how much RAM is left for sound data and OpenAL?

Reading the Apple docs, I haven’t really seen these metrics laid out yet. Apologies if I’ve missed the obvious.

T

Congrats on the new venture man – good stuff!

Have you done any metrics yet on rendering performance using OpenGL ES on the iPhone Hardware? I am wondering about things like polygon/texture budget needed to maintain 30Hz.

Also in the docs, it says that no more than 24MB of RAM should be allocated to texture and geometry. Do you know how much RAM is left for executable code at that point?

Likewise for sound – if you’re using 24MB for visuals, how much RAM is left for sound data and OpenAL?

Reading the Apple docs, I haven’t really seen these metrics laid out yet. Apologies if I’ve missed the obvious.

T

Congrats on the new venture man – good stuff!

Have you done any metrics yet on rendering performance using OpenGL ES on the iPhone Hardware? I am wondering about things like polygon/texture budget needed to maintain 30Hz.

Also in the docs, it says that no more than 24MB of RAM should be allocated to texture and geometry. Do you know how much RAM is left for executable code at that point?

Likewise for sound – if you’re using 24MB for visuals, how much RAM is left for sound data and OpenAL?

Reading the Apple docs, I haven’t really seen these metrics laid out yet. Apologies if I’ve missed the obvious.

T