public static final Image SCREEN_SHOT_DISABLE = getPngImage("toolbar_screen_shot_disable"); //$NON-NLS-1$\r
\r
/* setting */\r
-- public static final Image TARGET_MOBILE_2_3 = getPngImage("feature_target_mobile"); //$NON-NLS-1$\r
- public static final Image TARGET_TV_0_1 = getPngImage("feature_target_tv"); //$NON-NLS-1$\r
- public static final Image TARGET_WEARABLE_2_3 = getPngImage("feature_target_wearable"); //$NON-NLS-1$\r
++ public static final Image TARGET_NAME_MOBILE_2_3 = getPngImage("feature_target_mobile"); //$NON-NLS-1$\r
+ public static final Image TARGET_NAME_TV_1_0 = getPngImage("feature_target_tv"); //$NON-NLS-1$\r
- public static final Image TARGET_WEARABLE_2_3 = getPngImage("feature_target_wearable"); //$NON-NLS-1$\r
++ public static final Image TARGET_NAME_WEARABLE_2_3 = getPngImage("feature_target_wearable"); //$NON-NLS-1$\r
\r
public static final Image TEMPLATE_BOTTLENECK_ANALYSIS = getPngImage("feature_template_bottleneck"); //$NON-NLS-1$\r
public static final Image TEMPLATE_MEMORY_LEAK = getPngImage("feature_template_memoryleaks"); //$NON-NLS-1$\r
-mobile-2.3|System|0||Description : System|||||||
-mobile-2.3|System information sampling periodic|2|System|Description : System information sampling periodic|||100|1000|1000||
-mobile-2.3|System CPU|1|System|Description : System CPU|Timeline|CPU-CPU core-CPU frequency||||336|1
-mobile-2.3|System memory|1|System|Description : System memory|Timeline|Process Size-Memory-Heap allocation||||96|1
-mobile-2.3|System processes|1|System|Description : System processes|Timeline|CPU||||336|1
-mobile-2.3|System disk|1|System|Description : System disk|Timeline|Disk IO||||512|1
-mobile-2.3|System network|1|System|Description : System network|Timeline|Network IO||||1024|1
-mobile-2.3|System device|1|System|Description : System device|Timeline|Device||||2048|1
-mobile-2.3|System energy|1|System|Description : System energy|Timeline|Energy||||4096|1
-mobile-2.3|Function profiling|0||Description : Function Profiling|Timeline-Summary|||||4|1
-mobile-2.3|Function sampling|0||Description : Function sampling|Summary|||||524288|1
-mobile-2.3|Function profiling sampling periodic|2|Function sampling|Description : Function profiling sampling periodic|||1|1000|10||
-mobile-2.3|Memory allocation|0||Description : Memory allocation|Timeline-Summary|Heap allocation||||8|1
-mobile-2.3|File analysis|0||Description : File analysis|File|||||16|1
-mobile-2.3|Thread analysis|0||Description : Thread analysis|Thread|||||32|1
-mobile-2.3|Network analysis|0||Description : Network analysis|Network|||||131072|1
-mobile-2.3|OpenGL ES analysis|0||Description : OpenGL ES analysis|OpenGL|||||262144|1
-mobile-2.3|Screenshot|0||Description : Screenshot|Timeline|Screenshot||||128|1
-mobile-2.3|On scene transition|2|Screenshot|Description : On scene transition|||||1||
-mobile-2.3|periodically|2|Screenshot|Description : periodically|||1|100|10||
-mobile-2.3|UI event|0||Description : UI event|Timeline|UI event||||256|1
-mobile-2.3|Recording|0||Description : Recording||||||512|1
+mobile-2.3|System|0||Description : System||||||||
+mobile-2.3|System information sampling periodic|2|System|Description : System information sampling periodic|||100|1000|1000|||
+mobile-2.3|System memory|1|System|Description : System memory|Timeline|Process Size-Memory-Heap allocation|||||32|1
+mobile-2.3|System processes|1|System|Description : System processes|Timeline|CPU|||||256|1
+mobile-2.3|System disk|1|System|Description : System disk|Timeline|Disk IO|||||512|1
+mobile-2.3|System network|1|System|Description : System network|Timeline|Network IO|||||1024|1
+mobile-2.3|System device|1|System|Description : System device|Timeline|Device|||||2048|1
+mobile-2.3|System energy|1|System|Description : System energy|Timeline|Energy|||||4096|1
+mobile-2.3|Function profiling|0||Description : Function Profiling|Timeline-Summary|||||4||1
+mobile-2.3|Function sampling|0||Description : Function sampling|Summary|||||524288||1
+mobile-2.3|Function profiling sampling periodic|2|Function sampling|Description : Function profiling sampling periodic|||1|1000|10|||
+mobile-2.3|Memory allocation|0||Description : Memory allocation|Timeline-Summary|Heap allocation||||8||1
+mobile-2.3|File analysis|0||Description : File analysis|File|||||1040||1
+mobile-2.3|Thread analysis|0||Description : Thread analysis|Thread|||||32|128|1
+mobile-2.3|Network analysis|0||Description : Network analysis|Network|||||131072||1
+mobile-2.3|OpenGL ES analysis|0||Description : OpenGL ES analysis|OpenGL|||||262144||1
+mobile-2.3|Screenshot|0||Description : Screenshot|Timeline|Screenshot||||128||1
+mobile-2.3|On scene transition|2|Screenshot|Description : On scene transition|||||1|||
+mobile-2.3|periodically|2|Screenshot|Description : periodically|||1|100|10|||
+mobile-2.3|UI event|0||Description : UI event|Timeline|UI event||||256||1
+mobile-2.3|Recording|0||Description : Recording||||||512||1
+mobile-2.3|Context switch|0||Description : Context switch|Kernel|||||65536||1
+mobile-2.3|System call|0||Description : System call||||||||
+mobile-2.3|System call file|1|System call|Description : System call file|Timeline|||||1024||1
+mobile-2.3|System call ipc|1|System call|Description : System call ipc|Timeline|||||2048||1
+mobile-2.3|System call process|1|System call|Description : System call process|Timeline|||||4096||1
+mobile-2.3|System call signal|1|System call|Description : System call signal|Timeline|||||8192||1
+mobile-2.3|System call network|1|System call|Description : System call network|Timeline|||||16384||1
+mobile-2.3|System call desc|1|System call|Description : System call desc|Timeline|||||32768||1
+mobile-2.3|Inside the platform|0||Description : Inside the platform||||||||
+mobile-2.3|Inside the platform memory|1|Inside the platform|Description : Inside the platform memory|Timeline-Summary|Heap allocation||||268435456||1
+mobile-2.3|Inside the platform file|1|Inside the platform|Description : Inside the platform file|File|||||536870912||1
+mobile-2.3|Inside the platform thread|1|Inside the platform|Description : Inside the platform thread|Thread|||||1073741824||1
+mobile-2.3|Inside the platform network|1|Inside the platform|Description : Inside the platform network|Network||||||1|1
+mobile-2.3|Inside the platform openGL|1|Inside the platform|Description : Inside the platform openGL|OpenGL||||||2|1
+wearable-2.3|System|0||Description : System||||||||
+wearable-2.3|System information sampling periodic|2|System|Description : System information sampling periodic|||100|1000|1000|||
+wearable-2.3|System memory|1|System|Description : System memory|Timeline|Process Size-Memory-Heap allocation|||||32|1
+wearable-2.3|System processes|1|System|Description : System processes|Timeline|CPU|||||256|1
+wearable-2.3|System disk|1|System|Description : System disk|Timeline|Disk IO|||||512|1
+wearable-2.3|System network|1|System|Description : System network|Timeline|Network IO|||||1024|1
+wearable-2.3|System device|1|System|Description : System device|Timeline|Device|||||2048|1
+wearable-2.3|System energy|1|System|Description : System energy|Timeline|Energy|||||4096|1
+wearable-2.3|Function profiling|0||Description : Function Profiling|Timeline-Summary|||||4||1
+wearable-2.3|Function sampling|0||Description : Function sampling|Summary|||||524288||1
+wearable-2.3|Function profiling sampling periodic|2|Function sampling|Description : Function profiling sampling periodic|||1|1000|10|||
+wearable-2.3|Memory allocation|0||Description : Memory allocation|Timeline-Summary|Heap allocation||||8||1
+wearable-2.3|File analysis|0||Description : File analysis|File|||||1040||1
+wearable-2.3|Thread analysis|0||Description : Thread analysis|Thread|||||32|128|1
+wearable-2.3|Network analysis|0||Description : Network analysis|Network|||||131072||1
+wearable-2.3|OpenGL ES analysis|0||Description : OpenGL ES analysis|OpenGL|||||262144||1
+wearable-2.3|Screenshot|0||Description : Screenshot|Timeline|Screenshot||||128||1
+wearable-2.3|On scene transition|2|Screenshot|Description : On scene transition|||||1|||
+wearable-2.3|periodically|2|Screenshot|Description : periodically|||1|100|10|||
+wearable-2.3|UI event|0||Description : UI event|Timeline|UI event||||256||1
+wearable-2.3|Recording|0||Description : Recording||||||512||1
+wearable-2.3|Context switch|0||Description : Context switch|Kernel|||||65536||1
+wearable-2.3|System call|0||Description : System call||||||||
+wearable-2.3|System call file|1|System call|Description : System call file|Timeline|||||1024||1
+wearable-2.3|System call ipc|1|System call|Description : System call ipc|Timeline|||||2048||1
+wearable-2.3|System call process|1|System call|Description : System call process|Timeline|||||4096||1
+wearable-2.3|System call signal|1|System call|Description : System call signal|Timeline|||||8192||1
+wearable-2.3|System call network|1|System call|Description : System call network|Timeline|||||16384||1
+wearable-2.3|System call desc|1|System call|Description : System call desc|Timeline|||||32768||1
+wearable-2.3|Inside the platform|0||Description : Inside the platform||||||||
+wearable-2.3|Inside the platform memory|1|Inside the platform|Description : Inside the platform memory|Timeline-Summary|Heap allocation||||268435456||1
+wearable-2.3|Inside the platform file|1|Inside the platform|Description : Inside the platform file|File|||||536870912||1
+wearable-2.3|Inside the platform thread|1|Inside the platform|Description : Inside the platform thread|Thread|||||1073741824||1
+wearable-2.3|Inside the platform network|1|Inside the platform|Description : Inside the platform network|Network||||||1|1
+wearable-2.3|Inside the platform openGL|1|Inside the platform|Description : Inside the platform openGL|OpenGL||||||2|1
- tv-0.1|System|0||Description : System||||||||
- tv-0.1|System information sampling periodic|2|System|Description : System information sampling periodic|||100|1000|1000|||
- tv-0.1|System memory|1|System|Description : System memory|Timeline|Process Size-Memory-Heap allocation|||||32|1
- tv-0.1|System processes|1|System|Description : System processes|Timeline|CPU|||||256|1
- tv-0.1|System disk|1|System|Description : System disk|Timeline|Disk IO|||||512|1
- tv-0.1|System network|1|System|Description : System network|Timeline|Network IO|||||1024|1
- tv-0.1|System device|1|System|Description : System device|Timeline|Device|||||2048|1
- tv-0.1|System energy|1|System|Description : System energy|Timeline|Energy|||||4096|1
- tv-0.1|Function profiling|0||Description : Function Profiling|Timeline-Summary|||||4||1
- tv-0.1|Function sampling|0||Description : Function sampling|Summary|||||524288||1
- tv-0.1|Function profiling sampling periodic|2|Function sampling|Description : Function profiling sampling periodic|||1|1000|10|||
- tv-0.1|Memory allocation|0||Description : Memory allocation|Timeline-Summary|Heap allocation||||8||1
- tv-0.1|File analysis|0||Description : File analysis|File|||||1040||1
- tv-0.1|Thread analysis|0||Description : Thread analysis|Thread|||||32|128|1
- tv-0.1|Network analysis|0||Description : Network analysis|Network|||||131072||1
- tv-0.1|OpenGL ES analysis|0||Description : OpenGL ES analysis|OpenGL|||||262144||1
- tv-0.1|Screenshot|0||Description : Screenshot|Timeline|Screenshot||||128||1
- tv-0.1|On scene transition|2|Screenshot|Description : On scene transition|||||1|||
- tv-0.1|periodically|2|Screenshot|Description : periodically|||1|100|10|||
- tv-0.1|UI event|0||Description : UI event|Timeline|UI event||||256||1
- tv-0.1|Recording|0||Description : Recording||||||512||1
- tv-0.1|Context switch|0||Description : Context switch|Kernel|||||65536||1
- tv-0.1|System call|0||Description : System call||||||||
- tv-0.1|System call file|1|System call|Description : System call file|Timeline|||||1024||1
- tv-0.1|System call ipc|1|System call|Description : System call ipc|Timeline|||||2048||1
- tv-0.1|System call process|1|System call|Description : System call process|Timeline|||||4096||1
- tv-0.1|System call signal|1|System call|Description : System call signal|Timeline|||||8192||1
- tv-0.1|System call network|1|System call|Description : System call network|Timeline|||||16384||1
- tv-0.1|System call desc|1|System call|Description : System call desc|Timeline|||||32768||1
- tv-0.1|Inside the platform|0||Description : Inside the platform||||||||
- tv-0.1|Inside the platform memory|1|Inside the platform|Description : Inside the platform memory|Timeline-Summary|Heap allocation||||268435456||1
- tv-0.1|Inside the platform file|1|Inside the platform|Description : Inside the platform file|File|||||536870912||1
- tv-0.1|Inside the platform thread|1|Inside the platform|Description : Inside the platform thread|Thread|||||1073741824||1
- tv-0.1|Inside the platform network|1|Inside the platform|Description : Inside the platform network|Network||||||1|1
- tv-0.1|Inside the platform openGL|1|Inside the platform|Description : Inside the platform openGL|OpenGL||||||2|1
++tv-1.0|System|0||Description : System||||||||
++tv-1.0|System information sampling periodic|2|System|Description : System information sampling periodic|||100|1000|1000|||
++tv-1.0|System memory|1|System|Description : System memory|Timeline|Process Size-Memory-Heap allocation|||||32|1
++tv-1.0|System processes|1|System|Description : System processes|Timeline|CPU|||||256|1
++tv-1.0|System disk|1|System|Description : System disk|Timeline|Disk IO|||||512|1
++tv-1.0|System network|1|System|Description : System network|Timeline|Network IO|||||1024|1
++tv-1.0|System device|1|System|Description : System device|Timeline|Device|||||2048|1
++tv-1.0|System energy|1|System|Description : System energy|Timeline|Energy|||||4096|1
++tv-1.0|Function profiling|0||Description : Function Profiling|Timeline-Summary|||||4||1
++tv-1.0|Function sampling|0||Description : Function sampling|Summary|||||524288||1
++tv-1.0|Function profiling sampling periodic|2|Function sampling|Description : Function profiling sampling periodic|||1|1000|10|||
++tv-1.0|Memory allocation|0||Description : Memory allocation|Timeline-Summary|Heap allocation||||8||1
++tv-1.0|File analysis|0||Description : File analysis|File|||||1040||1
++tv-1.0|Thread analysis|0||Description : Thread analysis|Thread|||||32|128|1
++tv-1.0|Network analysis|0||Description : Network analysis|Network|||||131072||1
++tv-1.0|OpenGL ES analysis|0||Description : OpenGL ES analysis|OpenGL|||||262144||1
++tv-1.0|Screenshot|0||Description : Screenshot|Timeline|Screenshot||||128||1
++tv-1.0|On scene transition|2|Screenshot|Description : On scene transition|||||1|||
++tv-1.0|periodically|2|Screenshot|Description : periodically|||1|100|10|||
++tv-1.0|UI event|0||Description : UI event|Timeline|UI event||||256||1
++tv-1.0|Recording|0||Description : Recording||||||512||1
++tv-1.0|Context switch|0||Description : Context switch|Kernel|||||65536||1
++tv-1.0|System call|0||Description : System call||||||||
++tv-1.0|System call file|1|System call|Description : System call file|Timeline|||||1024||1
++tv-1.0|System call ipc|1|System call|Description : System call ipc|Timeline|||||2048||1
++tv-1.0|System call process|1|System call|Description : System call process|Timeline|||||4096||1
++tv-1.0|System call signal|1|System call|Description : System call signal|Timeline|||||8192||1
++tv-1.0|System call network|1|System call|Description : System call network|Timeline|||||16384||1
++tv-1.0|System call desc|1|System call|Description : System call desc|Timeline|||||32768||1
++tv-1.0|Inside the platform|0||Description : Inside the platform||||||||
++tv-1.0|Inside the platform memory|1|Inside the platform|Description : Inside the platform memory|Timeline-Summary|Heap allocation||||268435456||1
++tv-1.0|Inside the platform file|1|Inside the platform|Description : Inside the platform file|File|||||536870912||1
++tv-1.0|Inside the platform thread|1|Inside the platform|Description : Inside the platform thread|Thread|||||1073741824||1
++tv-1.0|Inside the platform network|1|Inside the platform|Description : Inside the platform network|Network||||||1|1
++tv-1.0|Inside the platform openGL|1|Inside the platform|Description : Inside the platform openGL|OpenGL||||||2|1
-Target List|mobile-2.3
+Version|0.1
- Target List|mobile-2.3|wearable-2.3|tv-0.1
++Target List|mobile-2.3|wearable-2.3|tv-1.0
Selected Target|mobile-2.3
-Selected Chart List|CPU frequency|CPU|CPU core
+Selected Chart List|CPU|CPU core|CPU frequency
Show Initial|false
Auto Stop|false
+Default Chart List|CPU|CPU core|CPU frequency
+Default Swap Value|0|80
Selected Template|mobile-2.3|Bottleneck
-Selected FeatureList|mobile-2.3|System|System CPU|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
-Available Chart List|mobile-2.3|CPU|CPU core|CPU frequency|Heap allocation|Process Size|Memory|Screenshot|UI event|Disk IO|Network IO|Device|Energy
+Selected FeatureList|mobile-2.3|System|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
+Available Chart List|mobile-2.3|CPU|CPU core|CPU frequency|Heap allocation|Process Size|Memory|Screenshot|UI event|Disk IO|Network IO|Device|Energy
+Selected Template|wearable-2.3|Bottleneck
+Selected FeatureList|wearable-2.3|System|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
+Available Chart List|wearable-2.3|CPU|CPU core|CPU frequency|Heap allocation|Process Size|Memory|Screenshot|UI event|Disk IO|Network IO|Device|Energy
- Selected Template|tv-0.1|Bottleneck
- Selected FeatureList|tv-0.1|System|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
- Available Chart List|tv-0.1|CPU|CPU core|CPU frequency|Heap allocation|Process Size|Memory|Screenshot|UI event|Disk IO|Network IO|Device|Energy
++Selected Template|tv-1.0|Bottleneck
++Selected FeatureList|tv-1.0|System|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
++Available Chart List|tv-1.0|CPU|CPU core|CPU frequency|Heap allocation|Process Size|Memory|Screenshot|UI event|Disk IO|Network IO|Device|Energy
-mobile-2.3|Bottleneck|This template shows where can be the most bottleneck point while you are using your program. With the CPU and process chart, you can easily find where the application uses the CPU a lot. And the function profiling and call trace information shows the bottleneck point with the view of function level.|System|System CPU|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
+mobile-2.3|Bottleneck|This template shows where can be the most bottleneck point while you are using your program. With the CPU and process chart, you can easily find where the application uses the CPU a lot. And the function profiling and call trace information shows the bottleneck point with the view of function level.|System|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
mobile-2.3|Memory Leaks|This template shows the memory leak detected by this tool. Normally, the leak list in the Summary shows the allocation list that is not yet freed. And with the range feature in the timeline chart, you can also check the leak candidates which are not freed in an appropriate position.|Memory allocation|System|System memory|System information sampling periodic:1000|Function profiling
-mobile-2.3|Process Activity|This template shows the overall activities of your concerning processes, which are process¡¯s CPU load and memory usage. And the function profiling is shown to help you to understand the detail activity of the process.|System|System CPU|System processes|System memory|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
+mobile-2.3|Process Activity|This template shows the overall activities of your concerning processes, which are process¡¯s CPU load and memory usage. And the function profiling is shown to help you to understand the detail activity of the process.|System|System processes|System memory|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
mobile-2.3|File|This template shows the operations(open, close, read, write and lock) of the files that were accessed by your application. It helps you to easily check the concurrent read/write access and the file lock waiting status of the processes for each file.|System|System disk|System information sampling periodic:1000|File analysis
-mobile-2.3|Thread Activity|This template measures CPU usage of threads, visualizes life-cycle of each thread and relationship between threads. It also analyzes critical section duration and waiting time of synchronization objects.|System|System CPU|System processes|System information sampling periodic:1000|Thread analysis
-mobile-2.3|Wait Status|This template shows various information that cause the process become wait status. With the CPU and process chart, you can distinguish the process is in busy status or wait status. If the process is waiting for the IO operation or lock, you can check it in the Network, File, and Thread analysis pages. |System|System CPU|System processes|System network|System disk|System information sampling periodic:1000|Thread analysis|Network analysis|File analysis
+mobile-2.3|Thread Activity|This template measures CPU usage of threads, visualizes life-cycle of each thread and relationship between threads. It also analyzes critical section duration and waiting time of synchronization objects.|System|System processes|System information sampling periodic:1000|Thread analysis
+mobile-2.3|Wait Status|This template shows various information that cause the process become wait status. With the CPU and process chart, you can distinguish the process is in busy status or wait status. If the process is waiting for the IO operation or lock, you can check it in the Network, File, and Thread analysis pages. |System|System processes|System network|System disk|System information sampling periodic:1000|Thread analysis|Network analysis|File analysis
mobile-2.3|Network|This template shows the TCP/UDP network activity of the glibc socket. The Network chart shows each session information. And you can check which API has been called in each session and can see the transmitted data, too.|System|System network|System information sampling periodic:1000|Network analysis
-mobile-2.3|OpenGL|This template shows a lot of detailed information of the openGL layer. It shows the FPS, render state, openGL calls, statistics and redundant usage of the API. These help you to optimize the performance of your application. We are supporting OpenGL ES 2.0 and EvasGL, now.|System|System CPU|System processes|System information sampling periodic:1000|Function profiling|Screenshot|periodically:10|OpenGL ES analysis
-mobile-2.3|Energy|This template inform you of power consumption of target device. you can see this information from Energy chart in Timeline page. Energy chart shows usage of Flash memory, CPU, LCD.|System|System CPU|System processes|System memory|System energy|System information sampling periodic:1000
-mobile-2.3|Custom|This template can be configured by selecting the desired features. If you change the feature in the other template will change custom template.
+mobile-2.3|OpenGL|This template shows a lot of detailed information of the openGL layer. It shows the FPS, render state, openGL calls, statistics and redundant usage of the API. These help you to optimize the performance of your application. We are supporting OpenGL ES 2.0 and EvasGL, now.|System|System processes|System information sampling periodic:1000|Function profiling|Screenshot|periodically:10|OpenGL ES analysis
+mobile-2.3|Energy|This template inform you of power consumption of target device. you can see this information from Energy chart in Timeline page. Energy chart shows usage of Flash memory, CPU, LCD.|System|System processes|System memory|System energy|System information sampling periodic:1000
+mobile-2.3|Custom|This template can be configured by selecting the desired features. If you change the feature in the other template will change custom template.
+wearable-2.3|Bottleneck|This template shows where can be the most bottleneck point while you are using your program. With the CPU and process chart, you can easily find where the application uses the CPU a lot. And the function profiling and call trace information shows the bottleneck point with the view of function level.|System|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
+wearable-2.3|Memory Leaks|This template shows the memory leak detected by this tool. Normally, the leak list in the Summary shows the allocation list that is not yet freed. And with the range feature in the timeline chart, you can also check the leak candidates which are not freed in an appropriate position.|Memory allocation|System|System memory|System information sampling periodic:1000|Function profiling
+wearable-2.3|Process Activity|This template shows the overall activities of your concerning processes, which are process¡¯s CPU load and memory usage. And the function profiling is shown to help you to understand the detail activity of the process.|System|System processes|System memory|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
+wearable-2.3|File|This template shows the operations(open, close, read, write and lock) of the files that were accessed by your application. It helps you to easily check the concurrent read/write access and the file lock waiting status of the processes for each file.|System|System disk|System information sampling periodic:1000|File analysis
+wearable-2.3|Thread Activity|This template measures CPU usage of threads, visualizes life-cycle of each thread and relationship between threads. It also analyzes critical section duration and waiting time of synchronization objects.|System|System processes|System information sampling periodic:1000|Thread analysis
+wearable-2.3|Wait Status|This template shows various information that cause the process become wait status. With the CPU and process chart, you can distinguish the process is in busy status or wait status. If the process is waiting for the IO operation or lock, you can check it in the Network, File, and Thread analysis pages. |System|System processes|System network|System disk|System information sampling periodic:1000|Thread analysis|Network analysis|File analysis
+wearable-2.3|Network|This template shows the TCP/UDP network activity of the glibc socket. The Network chart shows each session information. And you can check which API has been called in each session and can see the transmitted data, too.|System|System network|System information sampling periodic:1000|Network analysis
+wearable-2.3|OpenGL|This template shows a lot of detailed information of the openGL layer. It shows the FPS, render state, openGL calls, statistics and redundant usage of the API. These help you to optimize the performance of your application. We are supporting OpenGL ES 2.0 and EvasGL, now.|System|System processes|System information sampling periodic:1000|Function profiling|Screenshot|periodically:10|OpenGL ES analysis
+wearable-2.3|Energy|This template inform you of power consumption of target device. you can see this information from Energy chart in Timeline page. Energy chart shows usage of Flash memory, CPU, LCD.|System|System processes|System memory|System energy|System information sampling periodic:1000
+wearable-2.3|Custom|This template can be configured by selecting the desired features. If you change the feature in the other template will change custom template.
- tv-0.1|Bottleneck|This template shows where can be the most bottleneck point while you are using your program. With the CPU and process chart, you can easily find where the application uses the CPU a lot. And the function profiling and call trace information shows the bottleneck point with the view of function level.|System|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
- tv-0.1|Memory Leaks|This template shows the memory leak detected by this tool. Normally, the leak list in the Summary shows the allocation list that is not yet freed. And with the range feature in the timeline chart, you can also check the leak candidates which are not freed in an appropriate position.|Memory allocation|System|System memory|System information sampling periodic:1000|Function profiling
- tv-0.1|Process Activity|This template shows the overall activities of your concerning processes, which are process¡¯s CPU load and memory usage. And the function profiling is shown to help you to understand the detail activity of the process.|System|System processes|System memory|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
- tv-0.1|File|This template shows the operations(open, close, read, write and lock) of the files that were accessed by your application. It helps you to easily check the concurrent read/write access and the file lock waiting status of the processes for each file.|System|System disk|System information sampling periodic:1000|File analysis
- tv-0.1|Thread Activity|This template measures CPU usage of threads, visualizes life-cycle of each thread and relationship between threads. It also analyzes critical section duration and waiting time of synchronization objects.|System|System processes|System information sampling periodic:1000|Thread analysis
- tv-0.1|Wait Status|This template shows various information that cause the process become wait status. With the CPU and process chart, you can distinguish the process is in busy status or wait status. If the process is waiting for the IO operation or lock, you can check it in the Network, File, and Thread analysis pages. |System|System processes|System network|System disk|System information sampling periodic:1000|Thread analysis|Network analysis|File analysis
- tv-0.1|Network|This template shows the TCP/UDP network activity of the glibc socket. The Network chart shows each session information. And you can check which API has been called in each session and can see the transmitted data, too.|System|System network|System information sampling periodic:1000|Network analysis
- tv-0.1|OpenGL|This template shows a lot of detailed information of the openGL layer. It shows the FPS, render state, openGL calls, statistics and redundant usage of the API. These help you to optimize the performance of your application. We are supporting OpenGL ES 2.0 and EvasGL, now.|System|System processes|System information sampling periodic:1000|Function profiling|Screenshot|periodically:10|OpenGL ES analysis
- tv-0.1|Energy|This template inform you of power consumption of target device. you can see this information from Energy chart in Timeline page. Energy chart shows usage of Flash memory, CPU, LCD.|System|System processes|System memory|System energy|System information sampling periodic:1000
- tv-0.1|Custom|This template can be configured by selecting the desired features. If you change the feature in the other template will change custom template.
++tv-1.0|Bottleneck|This template shows where can be the most bottleneck point while you are using your program. With the CPU and process chart, you can easily find where the application uses the CPU a lot. And the function profiling and call trace information shows the bottleneck point with the view of function level.|System|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
++tv-1.0|Memory Leaks|This template shows the memory leak detected by this tool. Normally, the leak list in the Summary shows the allocation list that is not yet freed. And with the range feature in the timeline chart, you can also check the leak candidates which are not freed in an appropriate position.|Memory allocation|System|System memory|System information sampling periodic:1000|Function profiling
++tv-1.0|Process Activity|This template shows the overall activities of your concerning processes, which are process¡¯s CPU load and memory usage. And the function profiling is shown to help you to understand the detail activity of the process.|System|System processes|System memory|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
++tv-1.0|File|This template shows the operations(open, close, read, write and lock) of the files that were accessed by your application. It helps you to easily check the concurrent read/write access and the file lock waiting status of the processes for each file.|System|System disk|System information sampling periodic:1000|File analysis
++tv-1.0|Thread Activity|This template measures CPU usage of threads, visualizes life-cycle of each thread and relationship between threads. It also analyzes critical section duration and waiting time of synchronization objects.|System|System processes|System information sampling periodic:1000|Thread analysis
++tv-1.0|Wait Status|This template shows various information that cause the process become wait status. With the CPU and process chart, you can distinguish the process is in busy status or wait status. If the process is waiting for the IO operation or lock, you can check it in the Network, File, and Thread analysis pages. |System|System processes|System network|System disk|System information sampling periodic:1000|Thread analysis|Network analysis|File analysis
++tv-1.0|Network|This template shows the TCP/UDP network activity of the glibc socket. The Network chart shows each session information. And you can check which API has been called in each session and can see the transmitted data, too.|System|System network|System information sampling periodic:1000|Network analysis
++tv-1.0|OpenGL|This template shows a lot of detailed information of the openGL layer. It shows the FPS, render state, openGL calls, statistics and redundant usage of the API. These help you to optimize the performance of your application. We are supporting OpenGL ES 2.0 and EvasGL, now.|System|System processes|System information sampling periodic:1000|Function profiling|Screenshot|periodically:10|OpenGL ES analysis
++tv-1.0|Energy|This template inform you of power consumption of target device. you can see this information from Energy chart in Timeline page. Energy chart shows usage of Flash memory, CPU, LCD.|System|System processes|System memory|System energy|System information sampling periodic:1000
++tv-1.0|Custom|This template can be configured by selecting the desired features. If you change the feature in the other template will change custom template.
public class ConfigureLabels extends NLS {
private static final String BUNDLE_NAME = "org.tizen.dynamicanalyzer.nl.ConfigureLabels"; //$NON-NLS-1$
- // table
- public static String FEATURE_TABLE_TITLE;
- public static String FEATURE_TABLE_FEATURE_EMPTY;
- public static String FEATURE_TABLE_FEATURE_NAME;
- public static String FEATURE_DETAIL_TITLE;
- public static String FEATURE_DETAIL_SETTING_TITLE;
+ public static String AUTO;
+ public static String SAMPLING;
+ public static String SECOND;
+ public static String MS;
+
+ public static String DETAIL_FUNCTIONPROFILING;
+ public static String DETAIL_ALLOCATION;
+ public static String DETAIL_FILE;
+ public static String DETAIL_THREAD;
+ public static String DETAIL_USERINTERFACE;
+ public static String DETAIL_SNAPSHOT;
+ public static String DETAIL_EVENT;
+ public static String DETAIL_RECORDING;
+
+ public static String SETTING_DIALOG_DESCRIPTION;
+ public static String SETTING_DIALOG_TARGET_TITLE;
+ public static String SETTING_DIALOG_TEMPLATE_TITLE;
+ public static String SETTING_DIALOG_OVERHEAD_FIRST;
+ public static String SETTING_DIALOG_OVERHEAD_LAST;
+
+ public static String FEATURE_DIALOG_HEADER_TITLE;
+ public static String FEATURE_DIALOG_DESCRIPTION;
+ public static String FEATURE_DIALOG_FEATURE_TABLE_COLUMN_NAME;
- public static String TARGET_NAME_TV_0_1;
+ public static String SETTING_WARNING_MESSAGE_FILE_NOT_FOUND;
+ public static String SETTING_WARNING_MESSAGE_SETTING_FAIL;
+
+ public static String TARGET_NAME_MOBILE_2_3;
++ public static String TARGET_NAME_TV_1_0;
+ public static String TARGET_NAME_WEARABLE_2_3;
+
+ public static String TEMPLATE_NAME_BOTTLENECK;
+ public static String TEMPLATE_NAME_MEMORY_LEAKS;
+ public static String TEMPLATE_NAME_PROCESS_ACTIVITY;
+ public static String TEMPLATE_NAME_FILE;
+ public static String TEMPLATE_NAME_THREAD_ACTIVITY;
+ public static String TEMPLATE_NAME_WAIT_STATUS;
+ public static String TEMPLATE_NAME_NETWORK;
+ public static String TEMPLATE_NAME_OPEN_GL;
+ public static String TEMPLATE_NAME_ENERGY;
+ public static String TEMPLATE_NAME_CUSTOM;
+
+ public static String PAGE_NAME_TIME_LINE;
+ public static String PAGE_NAME_SUMMARY;
+ public static String PAGE_NAME_FILE;
+ public static String PAGE_NAME_THREAD;
+ public static String PAGE_NAME_NETWORK;
+ public static String PAGE_NAME_OPENGL;
+ public static String PAGE_NAME_KERNEL;
- public static String SETTING_TABLE_TITLE;
- public static String SETTING_WHITE;
- public static String SETTING_BLACK;
- public static String SETTING_CONFIGURATION_TITLE;
+ public static String FEATURE_NAME_SYSTEM; // 3.0 only
+ public static String FEATURE_NAME_SYSTEM_CPU; // 3.0 only
+ public static String FEATURE_NAME_SYSTEM_MEMORY; // 3.0 only
+ public static String FEATURE_NAME_SYSTEM_PROCESSES; // 3.0 only
+ public static String FEATURE_NAME_SYSTEM_DISK; // 3.0 only
+ public static String FEATURE_NAME_SYSTEM_NETWORK; // 3.0 only
+ public static String FEATURE_NAME_SYSTEM_DEVICE; // 3.0 only
+ public static String FEATURE_NAME_SYSTEM_ENERGY; // 3.0 only
+
+ public static String FEATURE_NAME_FUNCTION_PROFILING;
+ public static String FEATURE_NAME_FUNCTION_SAMPLING; // 3.0 only
+ public static String FEATURE_NAME_MEMORY_ALLOCATION;
+ public static String FEATURE_NAME_FILE;
+ public static String FEATURE_NAME_THREAD;
+ public static String FEATURE_NAME_NETWORK; // 3.0 only
+ public static String FEATURE_NAME_OPENGL; // 3.0 only
+ public static String FEATURE_NAME_SCREENSHOT;
+ public static String FEATURE_NAME_USER_EVENT;
+ public static String FEATURE_NAME_RECORDING;
+ public static String FEATURE_NAME_CONTEXT_SWITCH; // 3.0 only
+
+ public static String FEATURE_NAME_SYSTEM_CALL; // 3.0 only
+ public static String FEATURE_NAME_SYSTEM_CALL_FILE; // 3.0 only
+ public static String FEATURE_NAME_SYSTEM_CALL_IPC; // 3.0 only
+ public static String FEATURE_NAME_SYSTEM_CALL_PROCESS; // 3.0 only
+ public static String FEATURE_NAME_SYSTEM_CALL_SIGNAL; // 3.0 only
+ public static String FEATURE_NAME_SYSTEM_CALL_NETWORK; // 3.0 only
+ public static String FEATURE_NAME_SYSTEM_CALL_DESC; // 3.0 only
+
+ public static String FEATURE_NAME_INSIDE_THE_PLATFORM;
+ public static String FEATURE_NAME_INSIDE_THE_PLATFORM_MEMORY;
+ public static String FEATURE_NAME_INSIDE_THE_PLATFORM_FILE;
+ public static String FEATURE_NAME_INSIDE_THE_PLATFORM_THREAD;
+ public static String FEATURE_NAME_INSIDE_THE_PLATFORM_NETWORK;
+ public static String FEATURE_NAME_INSIDE_THE_PLATFORM_OPENGL;
+
+ public static String FEATURE_DETAIL_VALUE_SYSTEM_SAMPLING_RATE;
+ public static String FEATURE_DETAIL_VALUE_FUNCTION_PROFILING_SAMPLING_RATE;
+ public static String FEATURE_DETAIL_VALUE_SCREENSHOT_ON_SCENE_TRANSITION;
+ public static String FEATURE_DETAIL_VALUE_SCREENSHOT_PERIODICALLY;
- public static String WELCONE_ASK_USE_AGAIN;
- public static String SETTING_DIALOG_NOT_FOUND;
- public static String SETTING_DIALOG_FAIL_MESSAGE;
+ public static String FEATURE_DETAIL_VALUE_WARNING_FOR_EMPTY;
+ public static String FEATURE_DETAIL_VALUE_WARNING_FOR_CHARACTER;
+ public static String FEATURE_DETAIL_VALUE_WARNING_FOR_OUT_OF_RANGE;
+ public static String FEATURE_DETAIL_VALUE_WARNING_FOR_HAVE_TO_SET_MULTIPLE_OF_10MS_IN_SYSTEM_SAMPLING_RATE;
- public static String INCLUDE_INSIDE_CALL;
- public static String AUTO;
- public static String SECOND;
- public static String MS;
- public static String SAMPLING;
- public static String PERIODIC;
+ public static String SETTING_OPTION_TAB_DESCRIPTION;
- // features name
+ public static String SETTING_OPTION_SHOW_INITIAL;
+ public static String SETTING_OPTION_AUTO_STOP;
+
+ // TODO : this part is also deleted when the "org.tizen.dynamicanalyzer.ui.toolbar.configuration" package is deleted.
+ public static String FEATURE_TABLE_FEATURE_NAME;
public static String FEATURE_FUNCTION_PROFILING;
public static String FEATURE_FUNCTION_SAMPLING; // 3.0 only
public static String FEATURE_MEMORY_ALLOCATION;
VALUE_SHOULD_BE_IN_RANGE_FROM_100_TO_1000=value should be in range from 100 to 1000
YOU_HAVE_TO_SET_MULTIPLE_OF_10MS=you have to set multiple of 10ms
-TARGET_TITLE=Choose a target and template
-TARGETS=Targets
-TEMPLATE=Template
-OVERHEAD_FIRST=We expect X
-OVERHEAD_LAST=overhead
-FEATURES=Features
+SETTING_DIALOG_DESCRIPTION=Choose a target and template
+SETTING_DIALOG_TARGET_TITLE=Targets
+SETTING_DIALOG_TEMPLATE_TITLE=Template
+SETTING_DIALOG_OVERHEAD_FIRST=We expect X
+SETTING_DIALOG_OVERHEAD_LAST=overhead
+FEATURE_DIALOG_FEATURE_TABLE_COLUMN_NAME=Features
TARGET_NAME_MOBILE_2_3=mobile-2.3
- TARGET_NAME_TV_0_1=tv-0.1
+ TARGET_NAME_TV_1_0=tv-1.0
-TARGET_WEARABLE_2_3=wearable-2.3
+TARGET_NAME_WEARABLE_2_3=wearable-2.3
TEMPLATE_NAME_BOTTLENECK=Bottleneck
TEMPLATE_NAME_MEMORY_LEAKS=Memory Leaks
private void initDataList() {
targetHashMap = new HashMap<String, Image>();
-- targetHashMap.put(ConfigureLabels.TARGET_NAME_MOBILE_2_3, ImageResources.TARGET_MOBILE_2_3);
- targetHashMap.put(ConfigureLabels.TARGET_NAME_TV_0_1, ImageResources.TARGET_TV_0_1);
- targetHashMap.put(ConfigureLabels.TARGET_NAME_WEARABLE_2_3, ImageResources.TARGET_WEARABLE_2_3);
-
++ targetHashMap.put(ConfigureLabels.TARGET_NAME_MOBILE_2_3, ImageResources.TARGET_NAME_MOBILE_2_3);
+ targetHashMap.put(ConfigureLabels.TARGET_NAME_TV_1_0, ImageResources.TARGET_NAME_TV_1_0);
- targetHashMap.put(ConfigureLabels.TARGET_WEARABLE_2_3, ImageResources.TARGET_WEARABLE_2_3);
-
++ targetHashMap.put(ConfigureLabels.TARGET_NAME_WEARABLE_2_3, ImageResources.TARGET_NAME_WEARABLE_2_3);
templateHashMap = new HashMap<String, Image>();
templateHashMap.put(ConfigureLabels.TEMPLATE_NAME_BOTTLENECK, ImageResources.TEMPLATE_BOTTLENECK_ANALYSIS);
projects / sdk / tools / dynamic-analyzer.git / commitdiff