Hello everyone,
I've been curious about the influence my cpu clock is having on the actual fps ingame. So I made a little list.
Testing conditions:
-Galaxy S3 GT-I9300
-CF-rooted
-SiyahKernel s3-v1.9.1
-Stock Android international 4.1.2.
-Underclocked with NS Tools
-Untouched GPU Clock
-PPSSPP build: v.0.7.6-805-g2ef4a05
Settings:
-Skip Frames: no
-Enable Sound: yes
-Vertex Cache: no
-Hardware Transform: yes
-Stream VBO: no
-Media Engine: yes
-Linear Filtering: no
-Mipmapping: no
-Buffered Rendering: no
-Display Raw Frambuffer: no
-Anisotropic Filtering: no
-Texture Scaling: no
-Dynarec (JIT): yes
-Fast Memory: yes
-Encrypt Save: no
How I proceeded:
-freeze unnecessary apps via App Quarantine (such as Youtube, gmaps, gplay, g+, WhatsApp,etc.)
-kill tasks with ES-Taskmanager
-clear RAM in Android
-wait a few seconds
I ran every test twice loading the same savestate:
Practically I just ran around for 2-3 minutes dodging this monster as I did here:
http://www.youtube.com/watch?v=Pu1bRZ6YHHw
Here's the list:
500 MHZ - 35-42 fps - avg. 40
800 MHZ - 40-45 fps - avg. 43
1000 MHZ - 48-53 fps - avg. 51
1200 MHZ - 58-62 fps - avg. 60
As I'm limited to 60fps it didn't make sense to clock at stock 1,4 or even 1,6-1,8 GHZ. The "unlimited fps"option doesn't really work authentically, I guess.
As a result:
People always claim that OCing is totally useless as a mean to improve emulation speed but this little test showed that there actually is a noticable effect.
I'm not a developer so please correct me if I'm wrong.
I've been curious about the influence my cpu clock is having on the actual fps ingame. So I made a little list.
Testing conditions:
-Galaxy S3 GT-I9300
-CF-rooted
-SiyahKernel s3-v1.9.1
-Stock Android international 4.1.2.
-Underclocked with NS Tools
-Untouched GPU Clock
-PPSSPP build: v.0.7.6-805-g2ef4a05
Settings:
-Skip Frames: no
-Enable Sound: yes
-Vertex Cache: no
-Hardware Transform: yes
-Stream VBO: no
-Media Engine: yes
-Linear Filtering: no
-Mipmapping: no
-Buffered Rendering: no
-Display Raw Frambuffer: no
-Anisotropic Filtering: no
-Texture Scaling: no
-Dynarec (JIT): yes
-Fast Memory: yes
-Encrypt Save: no
How I proceeded:
-freeze unnecessary apps via App Quarantine (such as Youtube, gmaps, gplay, g+, WhatsApp,etc.)
-kill tasks with ES-Taskmanager
-clear RAM in Android
-wait a few seconds
I ran every test twice loading the same savestate:
Practically I just ran around for 2-3 minutes dodging this monster as I did here:
http://www.youtube.com/watch?v=Pu1bRZ6YHHw
Here's the list:
500 MHZ - 35-42 fps - avg. 40
800 MHZ - 40-45 fps - avg. 43
1000 MHZ - 48-53 fps - avg. 51
1200 MHZ - 58-62 fps - avg. 60
As I'm limited to 60fps it didn't make sense to clock at stock 1,4 or even 1,6-1,8 GHZ. The "unlimited fps"option doesn't really work authentically, I guess.
As a result:
People always claim that OCing is totally useless as a mean to improve emulation speed but this little test showed that there actually is a noticable effect.
I'm not a developer so please correct me if I'm wrong.
GT-I9300 | rooted | stock international 4.1.2 | overclocked on SiyahKernel s3-v1.9.1 (1,6 GHZ)|

