Author Topic: GPmark for Opendingux  (Read 6187 times)

Optimus (OP)

  • Posts: 107
GPmark for Opendingux
« on: September 04, 2012, 11:03:48 pm »
Hi there!

I just managed to port my GPmark benchmark specifically for Opendingux. I know there was another Dingux port of GPmark (that I think I haven't succeeded running) but I thought about making another one for Opendingux because I have recently installed it in my newly bought Dingoo (my old is broken :P) and there was not enough software to play with yet :)

It's also a crash course to get back to Dingoo development and might try to port my demos next and maybe other things who knows.

Enjoy!

Download from the gp32x archive
« Last Edit: September 04, 2012, 11:06:27 pm by Optimus »

Articus

  • Posts: 357
Re: GPmark for Opendingux
« Reply #1 on: September 07, 2012, 01:21:58 am »
Thank you for this tool!  Im running OD on a DT-a330 (using Stephanie's bootloader).
I got these results:

these are frames per second @336mhz (default clock)
Blitting Test:  197.4
Plasma:  141.7
RotoZoomer: 115.2
RotoZoomer Near:  143.5
RotoZoomer Far:  55.2
Radial Blur:  27.8
3d Bunny:  4.7

Here are the results @408mhz
Blitting Test:  248.7
Plasma:  176.4
RotoZoomer: 143.4
RotoZoomer Near:  178.7
RotoZoomer Far:  68.9
Radial Blur:  34.1
3d Bunny:  5.7

Just wanted to post this in case anyone is interested!  I dont really know what any of it means except, if I increase clock I should see graphical improvements (already knew this)!  Iam interested to know how it compared to the other Dingoos and other similar handhelds.

ruffnutts

  • Posts: 2653
Re: GPmark for Opendingux
« Reply #2 on: September 07, 2012, 06:02:26 pm »
@Articus I have a A330 in the cupboard with Stephanie's bootloader but my shoulder button is broke and I have the wifi controller... god only knows why I bought it not made very well waste of money for the extra 32meg of ram lol...

I guessing its the one the looks like a mini PSP?

ruffnutts

Articus

  • Posts: 357
Re: GPmark for Opendingux
« Reply #3 on: September 07, 2012, 07:27:03 pm »
@Ruffnutts- i too got it with a broken shoulder button.  I paid $34 dollars for it and included wireless gamepad.  Heck of a deal!  Ive been using it to pass the time while i wait for GCW Zero.  I sent GCW an email about the possibility of selling me a Zero case shell and buttons so i could house this a330 in it.  Or if anyone wants to sell a Ga330 case shell w/buttons, im interested.  I did fix the broken shoulder, but i want to house this in a different case!  If i have no luck i will mod into a ps1 controller.

ruffnutts

  • Posts: 2653
Re: GPmark for Opendingux
« Reply #4 on: September 07, 2012, 08:02:45 pm »
@Ruffnutts- i too got it with a broken shoulder button.  I paid $34 dollars for it and included wireless gamepad.  Heck of a deal!  Ive been using it to pass the time while i wait for GCW Zero.  I sent GCW an email about the possibility of selling me a Zero case shell and buttons so i could house this a330 in it.  Or if anyone wants to sell a Ga330 case shell w/buttons, im interested.  I did fix the broken shoulder, but i want to house this in a different case!  If i have no luck i will mod into a ps1 controller.

Lucky sod I paid ?70 for mine lol.. my shoulder button does sort of work but lost its click, you can buy these on the net easy there called tactile switches but my soldering skills are awful and my eyes aint very good lol

Articus

  • Posts: 357
Re: GPmark for Opendingux
« Reply #5 on: September 07, 2012, 08:52:33 pm »
Eyes not very good? You are gna need those, definately!!  Lol  :o

cutterjohn

  • !
  • Posts: 397
Re: GPmark for Opendingux
« Reply #6 on: September 07, 2012, 10:03:53 pm »
Hi there!

I just managed to port my GPmark benchmark specifically for Opendingux. I know there was another Dingux port of GPmark (that I think I haven't succeeded running) but I thought about making another one for Opendingux because I have recently installed it in my newly bought Dingoo (my old is broken :P) and there was not enough software to play with yet :)

It's also a crash course to get back to Dingoo development and might try to port my demos next and maybe other things who knows.

Enjoy!

Download from the gp32x archive
hmmm... I'll have to try compile this on my rpi and see what we get...

(I've had some good luck with the few emus that I could find with their modded sources from caannoo, dingoo, etc. working from the CLI with raspbian + rpi ... o.w. it takes me a bit of trial and error in figuring out compile settings, broken autogen scripts, fixing the emu, etc. I've only done frodo, vice, and atari800 so far... got bogged down with other things...)

cutterjohn

  • !
  • Posts: 397
Re: GPmark for Opendingux
« Reply #7 on: September 07, 2012, 10:28:43 pm »
Thank you for this tool!  Im running OD on a DT-a330 (using Stephanie's bootloader).
I got these results:

these are frames per second @336mhz (default clock)
Blitting Test:  197.4
Plasma:  141.7
RotoZoomer: 115.2
RotoZoomer Near:  143.5
RotoZoomer Far:  55.2
Radial Blur:  27.8
3d Bunny:  4.7

Here are the results @408mhz
Blitting Test:  248.7
Plasma:  176.4
RotoZoomer: 143.4
RotoZoomer Near:  178.7
RotoZoomer Far:  68.9
Radial Blur:  34.1
3d Bunny:  5.7

Just wanted to post this in case anyone is interested!  I dont really know what any of it means except, if I increase clock I should see graphical improvements (already knew this)!  Iam interested to know how it compared to the other Dingoos and other similar handhelds.
rpi @ 900MHz/500MHz mem raspbian 3.2.27+ kernel (hardfloat)
Blitting Test:  537.2
Plasma:  394.1
RotoZoomer: 289.4
RotoZoomer Near:  427.1
RotoZoomer Far:  165.5
Radial Blur:  46.3
3d Bunny:  8.7

Compiled w/o a hitch once the MIPS spec stuff in the makefile was commented out...

[EDIT]
I'll try my GCW Zero when it shows up... just can likely use the current opendingux setup...

wonder if I should mod it to use the GPU as well... didn't look at the source so I don't know how much that would entail...
[/EDIT]
« Last Edit: September 07, 2012, 10:31:14 pm by cutterjohn »

pcercuei

  • Posts: 1666
    • My devblog
Re: GPmark for Opendingux
« Reply #8 on: September 07, 2012, 10:53:49 pm »
Those numbers are extremely low. I used my own build of gpmark to benchmark OD, and I remember I got numbers higher than the ones for the Caanoo. Did you compile it with optimization flags?

zear

  • * Moderator
  • Posts: 2381
Re: GPmark for Opendingux
« Reply #9 on: September 08, 2012, 01:14:19 am »
Those numbers are extremely low. I used my own build of gpmark to benchmark OD, and I remember I got numbers higher than the ones for the Caanoo. Did you compile it with optimization flags?
Which then means the Caanoo version of gpmark might be unoptimized as well. So not comparable.

cutterjohn

  • !
  • Posts: 397
Re: GPmark for Opendingux
« Reply #10 on: September 08, 2012, 06:20:57 pm »
Those numbers are extremely low. I used my own build of gpmark to benchmark OD, and I remember I got numbers higher than the ones for the Caanoo. Did you compile it with optimization flags?
Code: [Select]
CFLAGS  = -g -pedantic -O3 -Wall -Wno-unused-variable $(INCLUDES) `sdl-config --cflags`
CXXFLAGS = $(CFLAGS)
LDFLAGS = `sdl-config --libs`
gcc (Debian 4.6.3-8+rpi1) 4.6.3

194/64 mem split

My native res is 1920x1080, so the bench ran in a smallish window of the screen, no idea but possibly the rest of the screen is being refreshed as well...

[EDIT]
As mentioned above I used the tarball meant for the Dingoo, but just removed the MIPS specific stuff(for cross-compile) from the Makefile.  Did not really look at the code at all, but I'll likely do so eventually as setup for Dingoo it responds to no keyboard inputs, so I'll at least have to change the exit code/keysyms.
[/EDIT]
« Last Edit: September 08, 2012, 06:25:20 pm by cutterjohn »

cutterjohn

  • !
  • Posts: 397
Re: GPmark for Opendingux
« Reply #11 on: September 08, 2012, 06:39:13 pm »
Well here's something interesting:
P8600 @ 2.4GHz Ubuntu 10.04 x86-64 4GB ATI Radeon HD mobility 4850/512MB GDDR3
Blitting Test:  349.2
Plasma:  231.0
RotoZoomer: 229.5
RotoZoomer Near:  226.6
RotoZoomer Far:  227.7
Radial Blur:  187.8
3d Bunny:  93.0

running in a 320x240 SDL window under X.org, Catalyst June drivers IIRC ("wonderful" folks at AMD have already dropped support for this GPU, meanwhile IIRC my nVidia drivers support back to GF2... ATI drivers just suck anyways, last time for an ATI GPU(notebook so no "easy" fix).)

methinks that this bench is not very good, or SDL sucks at this particular application of itself.

[EDIT]
rpi was framebuffer from "text"(it doesn't really have such a mode, it's "faked" by the GPU) mode(CLI/bash shell only).

I'll try this under "text" mode and see if it significantly differs...
[/EDIT]

[EDIT2]
Well, that was quick, I'm going to have to look into it later as it throws a segmentation fault, so I'll probably run it through gdb at some point or at least strace it... (last time it did that to me is because I tried running it from the build dir and it couldn't find it's demo datafile which I guessed correctly(who needs a readme? although ideally it would throw an error...)

Might be as simple as actually having to start in non-X mode(or quit X) altogether, but I'll check at some time later...
[/EDIT2]

[EDIT3]
Code: [Select]
Linux tester 2.6.32-42-generic #95-Ubuntu SMP Wed Jul 25 15:56:09 UTC 2012 x86_64 GNU/Linux
gcc (Ubuntu 4.4.3-4ubuntu5.1) 4.4.3
[/EDIT3]
« Last Edit: September 08, 2012, 06:59:59 pm by cutterjohn »

pcercuei

  • Posts: 1666
    • My devblog
Re: GPmark for Opendingux
« Reply #12 on: September 08, 2012, 06:47:16 pm »
Which then means the Caanoo version of gpmark might be unoptimized as well. So not comparable.

I don't think the Caanoo version can be optimized more. What the Caanoo needs is a proper OS. I got above 600fps on the blitting test on my A320, when rendering using hardware surfaces (I don't remember the other numbers though).

Articus

  • Posts: 357
Re: GPmark for Opendingux
« Reply #13 on: September 08, 2012, 06:51:04 pm »
Any idea why numbers on my DT-a330 are so low?

zear

  • * Moderator
  • Posts: 2381
Re: GPmark for Opendingux
« Reply #14 on: September 08, 2012, 07:16:16 pm »
when rendering using hardware surfaces
Then it's not comparable. If software surfaces were used for all the other gpmark ports, you need to list a software surface result to be able to compare with them.

pcercuei

  • Posts: 1666
    • My devblog
Re: GPmark for Opendingux
« Reply #15 on: September 08, 2012, 07:49:18 pm »
But the Caanoo OS doesn't use hardware surfaces, for instance. So I do compare what is comparable: builds of gpmark that use all the optimizations their respective OS provide. And the Dingoo on OD wins.

Optimus (OP)

  • Posts: 107
Re: GPmark for Opendingux
« Reply #16 on: September 10, 2012, 11:38:37 am »
My own results for comparison:

Dingoo A320 @336Mhz

Blitting test: 199.9
Plasma: 142.4
Rotozoomer: 115.8
Rotozoomer near: 144.3
Rotozoomer far: 55.4
Radial blur: 27.8
3d bunny: 4.7


Dingo A320 @408Mhz


Blitting test: 254.7
Plasma: 175.6
Rotozoomer: 143.0
Rotozoomer near: 178.1
Rotozoomer far: 67.9
Radial blur: 34.1
3d bunny: 5.8

Optimus (OP)

  • Posts: 107
Re: GPmark for Opendingux
« Reply #17 on: September 10, 2012, 11:46:36 am »
Those numbers are extremely low. I used my own build of gpmark to benchmark OD, and I remember I got numbers higher than the ones for the Caanoo. Did you compile it with optimization flags?

Strange. I always thought the Dingoo has slower CPU than the Caanoo (exceptions, it seems to show better results on radial blur test and far rotozoomer, that means less cache stalls, wow)

I use the -O3 on the flags as shown.
But yes, I have left SW_SURFACE on SDL video init. I should try today with HW_SURFACE and see the results.
I remember there were some hardware accelerated SDL libs on Caanoo too for SDL, maybe I've tried them, maybe not, I should try again. It would be interesting to see better results.

Optimus (OP)

  • Posts: 107
Re: GPmark for Opendingux
« Reply #18 on: September 10, 2012, 12:35:59 pm »
I've just tried HW_SURFACE and yes it shows much better results. (Blitting 472.2, Plasma 247.3, Rotozoomer 177,0, near 252.6, far 65.9, radial 29.9, bunny 4.7)

Only problem though is that it flickers like hell. Of course I thought, I should have enabled HW_DOUBLEBUF too. After enabling it though, it still flickers even if less and now it also vsyncs at 78fps, which is pointless for benchmarking. I guess when I get screen->pixels from SDL I always get vram pointer of a single page? Or not? I am using SDL_FLIP(screen) too, either at the end or after getting the pointer but before rendering. Same thing. I don't know whether the SDL implementation for HW is correct or if I should write my code in another way. Maybe render all the stuff to my own software buffer and then blit it by software to the screen->pixels pointer before calling SDL_FLIP? Then it could be just as slow as the old SW_SURFACE (Just tried. It's exactly the same results). Any ideas? (Of course the other idea for a benchmark is to forget SDL at all and dive directly into the hardware, though it wouldn't be so portable then)

Gotta find a solution for this, because I love the high results, but I don't like the flicker at all :(
« Last Edit: September 10, 2012, 12:55:48 pm by Optimus »

zear

  • * Moderator
  • Posts: 2381
Re: GPmark for Opendingux
« Reply #19 on: September 10, 2012, 12:39:03 pm »
Use -O2 instead of -O3 on the Dingoo. It gives better results.