A small guide…to J2me benchmark/test midlets
August 1st, 2006
Many times I’ve browsed the web to find the “best” midlet to do testing, finding supported JSR, and so on. So here is a small list of resources I’ve found on this topic. So feel free to add unlisted things, so I will be happy to extend the list.
- Calibrator
This one is doing a good job in many areas, testing all capacities of different JSR, RMS speed,video/audio capacities, etc…Results are send to a server, but this server side is really lacking of polishing. No organisation at all….That’s the only point to improve, but the midlet proven to be very useful. That’s my current favorite. - TastePhone
Here also, a lot of different tests are made, including RMS speed, copy speed, etc… Results are available on the result pages, but it might be in French only - JBenchmark
On of the older, probably good for speed checking, but limited forother informations. Speed issue is only a small part of the problem. But good website to browser the results…
Note that there are others benchmark now, JBenchmark2 (for MIDP2.0 devices) and JBenchmark3D (for JSR184). - GrinderBench:
position themseves as an “industry benchmark” developed by EEMBC, but coming very late in the market, and focused only on speed benchmark. - FPCBench: Update: The author of FPCBench posted some info on the bench as a comment of this post. It seems that it’s more than just speed. Unfortunatly, my main concern with this bench is that the UI is not as simple as Calibrator (why a Calculator is needed in such program), and results seems to be send through SMS…
- MicroCode: another project, not tested (thanks Wendong)
Other interesting resources:
I use frequently J2mepolish device database library, to quickly find if a handset support a specific JSR or not…. This database can be reused with j2mepolish to create specific build per device, or device family.
3 Comments Add your own
1. Wendong | August 2nd, 2006 at 5:15 am
I believe j2mepolish actually offers a Java ME client which covers testing like keycode, jsr, screen etc.
MicroCode project also collects a rich set of J2ME attributes in text files:
http://j2me-device-db.sourceforge.net
2. Davide | September 12th, 2006 at 3:28 pm
FPC Bench is not focused on speed only.
FPC Bench is a java benchmark to test and compare the performance of a phone with others phones. Differently from other benchmarks, FPC Bench results are not influenced from the screen resolution; this is a good way to get more reliable results.
FPC Bench is a complete test tool to test performance and features.
- CPU/Memory benchmark
- Check for total heap memory size
- Check for free heap memory size
- Check for full screen’s maximum resolution in a Java canvas
- Check for double buffering
- Check for RMS size
- Check for RMS speed
- Check for available profile/configuration
- Check for the latest APIs:
JSR 75: File System access API.
JSR 82: Bluetooth/OBEX API.
JSR 118: Mobile Information Device Profile API.
JSR 120: Wireless Messaging API (WMA 1.1).
JSR 135: Multimedia API (MMAPI)
JSR 139: Connected Limited Device Configuration 1.1
JSR 172: Wev service specification.
JSR 177: Security and Truste Services API.
JSR 179: Location API.
JSR 180: SIP API.
JSR 184: Mobile 3D Graphics.
JSR 185: Java Tech for Wireless Industry API.
JSR 205: Wireless Messaging API (WMA 2.0).
JSR 209: Advanced graphics and user interface.
JSR 211: Content Handler API.
JSR 226: Scalable 2D vector graphics for JavaME.
JSR 229: Payment API.
JSR 234: Advanced Multimedia API.
JSR 238: Mobile internationalization API.
JSR 239: Java binding for OpenGL ES.
JSR 257: Contactless communication API.
I think that is much more than a speed benchmark.
3. TomSoft » MobileZoo&hellip | October 5th, 2006 at 9:38 pm
[…] One of the initial idea (I am just over simplifiying, as there are many ideas in the air here!) was the following: instead of creating specific benchmark to provide information about handsets, or to create your own code to gather this information and store it on your server, why not provide a service for this? The ideas is to create a small library (less than 8kb) that can be easily embedded on most (if not all) J2me application. The library than gather the maximum of information about the handset and send them to a server. This server then maintains a database about handset capacities, supported JSR, configuration, etc…. There are multiple benefits on this approach: […]
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed