Overclocking aficionados know the problem-an overclocked CPU must be loaded if you want information about stability. Also, most benchmarking utilities for Palm OS dont focus on the processor, but rather on system performance as whole(a good thing usually, read more here). However, Palmpi does just that.
Calculating Pi(the circle number 3.141, you need it for calculating circle areas(radius squared times pi) and other data…) is very processor intensive. Since pi has an infinite amount of decimal places, there is an infinite lot of calculating involved if you work with enough decimals. Palmpi allows you to calculate up to 4680 digits-this can keep a T3 busy for a few minutes. The main screen looks like this:
![]()
If you click Benchmark, the program computes 400 decimals, which takes up to ten seconds on an ARM machine. The benchmark result is pretty constant, and can be used for comparing two boxen-if the Palmpi version is the same. Minimal changes may be introduced because the program does not work ARM native-PACE has a small influence as well.
![]()
Here are a few values for 0.2a-please post a comment with your values:
| Device | Time |
|---|---|
| Palm IIIc | 20.65 sec |
| Palm V | 28.01 sec |
| Palm Vii prototype | 29.88 sec |
| Tungsten E2 | 5.76 sec |
| Tungsten T3 | 2.87 sec |
| Tungsten T5 | 2.75 sec(user submitted) |
| Tungsten TX | 3.67 sec(user submitted) |
| WristPDA | 8.99 sec |
The start calc button calculates the amount of decimal places you specify-if you specify the maximum(1170), you have a nice stress test for your CPU-better than playing a video because of the constant, full load. My TE2 worked whooping 747.88 seconds on the calculations and powered off after finishing-if the handheld doesn’t power off after some time, the processor got too hot…
This test covered version 0.2a, we archived the program on Tamoggemon.com in case it ever goes offline.
Overall, don’t ask me why, but I like this tool. The benchmark is extremely CPU-centric, and the stress feature can come in handy…
Übertaktspezialisten kennen das Problem, dass eine übertaktete CPU geprüft werden muss wenn man Informationen über die Stabilitätwissen will. PalmPi tut dies durch Errechnung der Kreiszahl pi (benötigt zur Errechnung von Flächen), was sehr rechenintensiv ist. Da die Zahl unendlich viele Nachkommastellen hat kann unendlich viel gerechnet werden wenn man mit genug Nachkommastellen rechnet. PalmPi erlaubt bis zu 4680 Stellen - was bei einem T3 mehrere Minuten dauern kann. Das Hauptbild sieht so aus:
![]()
Wenn Sie auf Benchmark klicken, werden 400 Nachkommastellen errechnet, was auf einem ARM-Gerät bis zu zehn Sekunden dauert. Das Ergebnis ist ziemlich genau und kann zum Vergleich zweier Geräte genutzt werden - wenn die gleiche PalmPi-Version genutzt wird. Kleine Änderungen müssen vielleicht getan werden, weil das Programm nicht ARM-nativ läuft: PACE hat einen kleinen Einfluss.
![]()
Hier ein paar Werte von Version 0.2a. Bitte kommentieren Sie mit Ihren Werten:
| Gerät | Zeit [Sekunden} |
|---|---|
| Palm IIIc | 20.65 |
| Palm V | 28.01 |
| Palm Vii Prototyp | 29.88 |
| Tungsten E2 | 5.76 |
| Tungsten T3 | 2.87 |
| Tungsten T5 | 2.75 (von einem Leser) |
| Tungsten TX | 3.67 (von einem Leser) |
Wenn man die maximale Anzahl Nachkommastellen einstellt (1170), hat die CPU viel zu tun, sogar mehr als bei einem Video. Mein T|E2 gatte 747,88 Sekunden lang zu tun, dann war er fertig und ging aus.
Die Version aus diesem Test, 0.2a ist hier archiviert falls das Programm irgendwann offline gehen sollte.
Fragen Sie mich nich warum - aber ich mag das Programm…









2,87 secs on my T3 :-).
Hi,
didn’t I say it-the benchmark values are very well reproduceable?
Thanks for talking back!
Tam Hanna
hehe, I would rather play a round of Dxxm to stress test my processor
T5: 2.75 s
Full 1170 on my TX clocked to 585mhz: 255.45
Benchmark at same speed: 1.95
Benchmark at standard speed (312mhz): 3.67
Hi,
Palm IIIc:20.65 secs for benchmark
I gotta update that list…
Best regards and thanks for all the values
Tam Hanna
Hi,
Palm Vii prototype:
29.88secs
Best regards
Tam Hanna
Sony Clie TH55 E 9.68 sec.
Now with brand new TX: 3.68s
Hi Tam,
here are the results for:
Palm m515: 15.35 s
Clie SJ33: 7.82 s
Hi,
thank you very much!
Best regards
Tam Hanna
you’re welcome!
Just for your information PalmPi is still available and actually at 0.2b, get it here http://www.freewarepalm.com/calculator/palmpi.shtml
(I hope there will be no problem for posting 7.8the site !?)
Also i’ve done 3 more Benches:
Clie TJ37: 4.75
this one’s representative for the hole TJ-Series, because they have the same CPU !
Palm m125: 15.51 s
[LoRes, 33MHz DragonBall VZ]
Clie SL10: 12.94 s
[HiRes, 33MHz DragonBall SuperVZ]
In the last 2 measurements you can nicely see the difference between Motorola Dragonball VZ and SuperVZ Processors ! Maybe the SL10 could have better results, if it had a LoRes Screen.
best wishes
Hi,
PalmPi:
Sony Clié PEG-NX70V/U 5.74 sec
Sony Clié PEG-T675C 6.63 sec
Sony Clié PEG-NR70V/E 6.67 sec
Sony Clié PEG-SJ30/E 12.49 sec
Handspring Visor Neo 15.81 sec
Best regards
ancer
Hello,
My Palm Tungsten E takes 9.75 sec. for the benchmark at the default processor freq (252/2). After overcloking it to 372/2 it gives me 6.38 sec.
At the maximum working overclok frequency (192/1) it gives me 6.2 sec.
Best Regards
Francisco
And what about Zire22? Does anyone have results pls.?
Palm Tungsten T2: 9.39 secs
MY Palm IIIxe with My overclock Settings(Afterburner) With OS 4.1 and Speedups with Quickbits - comes to: 12.9 Seconds
I did use the Updated Versions 0.2b from http://www.freewarepalm.com/calculator/palmpi.shtml
And wowee 12.9 faster than a IIIc and V
and if Bullitt’s post says that a
Clie SL10: 12.94 s
[HiRes, 33MHz DragonBall SuperVZ] is as u see 12.94 and mines 12.9 - a bit faster than well I’m concluding that will the things I used it’s roughly a bit over 33mhz.
Yes My IIIxe is Quite Stable with these settings.
Esp. After getting rid of Bad Programs that caused resets, etc..
oh yeah forgot to add that I tested it about 3 times or so and it came out all the same.
oh crud - Afterburner is Set to 28mhz. Okay i’m done now.