Performance; Java; Figure 11: Test Case For Measuring Java Command Execution Throughput - Siemens Java TC65 User Manual

TC65 JAVA User's Guide
Strictly confidential / Released
5.9

Performance

The performance study was focused on comparable performance values under various
circumstances.
5.9.1

Java

This section gives information about the Java command execution throughput ("jPS"= Java
statements per second). The scope of this measurement is only the statement execution
time, not the execution delay (Java command on AT interface
reaction on GPIO).
Send URC (start performance test)
Generated frequency A
[reference sequence]
Generated frequency B
[measurement sequence]

Figure 11: Test case for measuring Java command execution throughput

The following Java instruction was used for calculation of the typical jPS:
value = ( 2 x number of calculation statements ) /
( ( 1 / frequencyB ) - ( 1 / frequencyA ) );
Measurement and calculation were done using:
•
duration of each loop = 600 s
•
number of calculation statements = 50 "
Instructions
(executed twice per pin cycle)
•
frequencyA as measured with a universal counter
•
frequencyB as measured with a universal counter
The reference loop has the same structure as the measurement loop except that the
measurement sequence is moved.
State
TC65 module in IDLE mode / Not connected
CSD connection
Since only a small amount of Java code is executed in this test, it is easily optimized by the
CLDC's HI just-in-time compiler. More complex applications might not reach that execution
speed.
TC65 JAVA User's Guide_V05
Change
Output pin output
pin level
result=(CONSTANT_VALUE/variable_value);
jPS-Value (mean)
~49000
~46000
Page 29 of 90
s
Java instruction execution
Test MIDlet
ATCommandListener.ATEvent()
Reference loop (for frequency A)
ATCommand.send(...)
Measurement loop (for frequency B)
Measurement sequence
ATCommand.send(...)
"-
26.09.2005