> Lies, damned lies, statistics and benchmarks. In about that order ;) hehehe, this is why we would not use any code put on the web pages of compiler vendors for sure ;) > An accurate indisputable benchmark I've found generally covers too narrow > an area to have a general use. For example pin toggling can be made a > fairly bulletproof benchmark but really doesn't matter unless you have a > particular need to toggle a pin quickly. this is one of our application, we are developing USB-JTAG for ARMs and toggling GPIO ports is quite important for this application, so AT91SAM7Sxx with build in USB and toggling twice faster GPIO ports is definitely winner for this kind of application > Likewise it's fairly easy to time > a null loop but that says little about how an application will behave. The > benchmark is that case is accurate, indisputable and pointless (or nearly so). > > A benchmark that purports to be generally useful generally is not accurate > and indisputable. The classic whetstone and dhrystone benchmarks have been > the subject of endless disputes (and IIRC compiler tweaking). I understand this, but I like what Richard @ FreeRTOS did: - test setup - 16bit math - 32bit math - floating math - bubble sort - data block memory move - conditional branching (let me know what elese we are missing here) these are the basic codes used in any application, so benchmarking them at different ARMs may be useful when you choose device for your future application and of course none of above can be considered as biased toward some compiler ot other, they will just show how good the compilers handle them > As a sage once said the only benchmark with any meaning is the application > you are going to run. completely agree, but if you see xx% improvement in your data memory move for instance on LPC (with 32 bit external data bus) toward OKI (with 16 bit external data bus) this will mean something when you decide which one to use in your time critical project who does transfer large amounts of memory blocks to the external memory right? we'll release the codes on our web together with the benchmarking so everyone will be able to re-produce these tests, we are just currious and don't want to prove that one ARM is better than other Best regards Tsvetan --- PCB prototypes for $26 at http://run.to/pcb (http://www.olimex.com/pcb) PCB any volume assembly (http://www.olimex.com/pcb/protoa.html) Development boards for ARM, AVR, PIC, MAXQ2000 and MSP430 (http://www.olimex.com/dev)
Message
Re: Banchmarking different ARMs
2005-02-27 by tsvetanusunov
Attachments
- No local attachments were found for this message.