TC65 JAVA User's Guide
Strictly confidential / Draft
5.8
Performance Statements
Scope of the performance study was getting comparable values that indicate the
performance under certain circumstances.
5.8.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 = 5 "
(executed twice per pin cycle)
•
frequencyA as measured with universal counter
•
frequencyB as measured with 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
These mean values may be sporadically reduced depending on dynamic conditions.
TC65 JAVA User's Guide_V01
Change
Output pin
output
pin level
result=(CONSTANT_VALUE/variable_value);
jPS-Value (mean)
~750 jPS
~450 jPS
Page 29 of 69
s
Java instruction execution
Test MIDlet
ATCommandListener.ATEvent()
Reference loop (for frequency A)
ATCommand.send(...)
Measurement loop (for frequency B)
Measurement sequence
ATCommand.send(...)
"-Instructions
11.03.2005