Cep Terminals GSM/GPRS TERMINAL CT63 JAVA 6203 用户手册
产品代码
6203
Java User’s Guide
5.12 Performance
39
wm_java_usersguide_v19
Page 35 of 109
2012-01-27
Confidential / Released
5.12.2
Pin I/O
The pin I/O test was designed to find out how fast a Java MIDlet can process URCs caused by
Pin I/O and react to these URCs. The URCs are generated by feeding an input pin with an
external frequency. As soon as the Java MIDlet is informed about the URC, it tries to regener-
ate the feeding frequency by toggling another output pin.
Pin I/O and react to these URCs. The URCs are generated by feeding an input pin with an
external frequency. As soon as the Java MIDlet is informed about the URC, it tries to regener-
ate the feeding frequency by toggling another output pin.
Figure 16: Test case for measuring Java MIDlet performance and handling pin-IO
The results of this test show that the delay from changing the state on the input pin to a state
change on the output pin is at least around 60 ms, but that time strongly depends on the amount
of garbage to collect and number of threads to be served by the virtual machine.
When doing this scenario using the Java GPIO API instead of ATCommand the delay goes
down to around half this value.
But still pin I/O is not really suitable for generating or detecting frequencies.
change on the output pin is at least around 60 ms, but that time strongly depends on the amount
of garbage to collect and number of threads to be served by the virtual machine.
When doing this scenario using the Java GPIO API instead of ATCommand the delay goes
down to around half this value.
But still pin I/O is not really suitable for generating or detecting frequencies.
5.12.3
Data Rates on RS-232 API
For details about the software platform and interfaces refer to
, "Software Platform".
This section summarises limitations and preconditions for performance when using the inter-
face CommConnection from package com.cinterion.io
face CommConnection from package com.cinterion.io
1
(refer to
).
The data rate on RS232 depends on the size of the buffer used for reading from and writing to
the serial interface. It is recommended that method read (byte[ ] b) be used for reading from
the serial interface. The recommended buffer size is 2kbyte. To achieve error free data trans-
mission the flow control on CommConnection must be switched on: <autorts> and <autocts>,
the same for the connected device.
the serial interface. It is recommended that method read (byte[ ] b) be used for reading from
the serial interface. The recommended buffer size is 2kbyte. To achieve error free data trans-
mission the flow control on CommConnection must be switched on: <autorts> and <autocts>,
the same for the connected device.
Different use cases are listed to give an idea of the attainable data rates. All applications for
measurement use only one thread and no additional activities other than those described were
carried out in parallel.
measurement use only one thread and no additional activities other than those described were
carried out in parallel.
1.
Up to TC65i v01.100 this package is named: com.siemens.icm.io.