J2ME String en/decoding
2010-03-23 02:10:26 by Luca TagliaferriToday we found out that few J2ME mobile phones were showing very poor performances when dealing with String deconding and enconding in UTF8 format. Hence we decided to check if it was possible to replace the native en/decoding functions with other optimized ones. The results are the ones shown below while the functions used for encoding and decoding can be downloaded here. As it can be seen in one of the cases the performace gains are impressive.
| Test / time (ms) | First phone (with native functions) | First phone (with optimized functions) |
| Test 1 | 7360 | 270 |
| Test 2 | 16477 | 372 |
| Test 3 | 7486 | 327 |
| Second phone (with native functions) | Secondo phone (with optimized functions) | |
| Test 1 | 262 | 133 |
| Test 2 | 369 | 122 |
| Test 3 | 372 | 202 |
Adesso studiamo il protocollo di Kioto^-1 per la Gran Bretagna
