WO2012033237A1 - 시스템 테스트 방법 - Google Patents
시스템 테스트 방법 Download PDFInfo
- Publication number
- WO2012033237A1 WO2012033237A1 PCT/KR2010/006068 KR2010006068W WO2012033237A1 WO 2012033237 A1 WO2012033237 A1 WO 2012033237A1 KR 2010006068 W KR2010006068 W KR 2010006068W WO 2012033237 A1 WO2012033237 A1 WO 2012033237A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- control block
- process control
- performance
- monitoring
- kernel
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
- G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
- G05B19/0428—Safety, monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3013—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is an embedded system, i.e. a combination of hardware and software dedicated to perform a certain function in mobile devices, printers, automotive or aircraft systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
- G06F11/3096—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents wherein the means or processing minimize the use of computing system or of computing system component resources, e.g. non-intrusive monitoring which minimizes the probe effect: sniffing, intercepting, indirectly deriving the monitored data from other directly available data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3644—Software debugging by instrumenting at runtime
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/23—Pc programming
- G05B2219/23283—Debugging, breakpoint
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/865—Monitoring of software
Definitions
- the present invention relates to a system test method.
- embedded software is software tailored to specific hardware and features. Most embedded software is designed to work optimally for constraints that do not afford system resources such as memory. Therefore, embedded software operating in the target environment has a problem that resource constraints are severe when operating the system compared to general software operating in the host environment.
- operation by various types of external input such as electronic signals or communication protocols is more important than operation by user commands such as menu selection. Therefore, there is a problem that it is difficult to apply the conventional software test techniques and test tools mainly operated by user commands to embedded software tests.
- the conventional software test technique is regarded as a symptom that represents a performance bottleneck only if high processor utilization persists in the performance test. In this case, if the processor utilization of a critical component falls below the basic performance, it is not regarded as an abnormal symptom. Therefore, there is a problem that the performance of the system can not be accurately tested.
- the present invention relates to a technique for a system test method that collects data for identifying performance bottlenecks and their causes and locations without affecting the operating environment of the system with minimal use of resources required for system operation.
- the present invention provides a system test method comprising identifying the location of a process control block, accessing the location of the process control block, and monitoring the performance elements of the process control block.
- the present invention has the advantage that it is possible to test the system without affecting the operating environment of the system by using the minimum resources necessary for operating the system.
- the present invention has the advantage that the system can be tested based on data input from the outside of the system.
- the present invention has the advantage of being able to test whether the bottleneck is a case even when the utilization rate of the processor falls below the reference.
- FIG. 1 is a flow chart showing a system test method according to the present invention.
- FIG. 2 is a program code for implementing a system test method according to the present invention.
- FIG. 3 illustrates the structure of a system that executes a system test method according to the present invention.
- the system test method of the present invention includes identifying a location of a process control block, accessing a location of the process control block, and monitoring a performance element of the process control block.
- a process control block refers to a data structure in which an operating system manages execution information of processes running in a system.
- the process control block may refer to a kernel data structure that manages the latest execution information of processes running in the system in real time.
- the system test method hooks a function table associated with the memory through a process control block to find a fault that has occurred in the memory of the system.
- system test method may analyze system performance by hacking system execution information such as page fault rate and processor utilization to analyze a performance bottleneck and its cause among data of a process control block.
- Process control block hacking minimizes test system performance degradation by centralizing the collection of data needed for performance analysis into one process control block.
- the present invention can satisfy the performance test requirements in the system operating environment while minimizing the system performance degradation as described above.
- system test method according to the present invention may be performed under the following conditions.
- Test Coverage Performance testing of a system in which all hardware and software components in the overall system are operating.
- Test Methods Run-time testing in a way that does not re-compile, re-link, or re-execute to ensure how the system runs.
- Tested A test on binaries loaded on the system without changing the original source / binary code of the software under test that does not contain additional code such as debugging information.
- Performance data Collects performance data that can take into account not only the processor but also memory, I / O, and network resources as the cause of performance bottlenecks.
- Bottleneck location tracking Collect location data for source-level analysis, such as functions, to locate performance bottlenecks.
- Performance Latency Minimize system performance latency due to testing to ensure real time operation.
- Code addition rate Minimize code addition rate due to testing to operate within limited resources.
- Process control blocks are kernel data structures that contain information about the execution of processes running on the system.
- the process control block also includes performance factors such as processor usage and free memory size to determine performance bottlenecks, and these values are always kept up to date by the kernel.
- the system test method according to the present invention can be used for performance analysis for developing agents that hack these values. Below we look at the performance factors and associated process control block structures needed to analyze the cause of performance bottlenecks.
- Performance refers to the extent to which a system or component performs its function within the constraints of a given system. Performance testing is an evaluation of whether a system meets specific performance requirements.
- a system's performance bottleneck is the performance degradation of the system due to competition for limited resources such as memory, I / O devices, and networks.
- the causes of system performance bottlenecks can vary, such as lack of resources, contention for shared resources, resource monopoly, misconfiguration of resources, or misbehaving resources.
- Page faults and memory usage are the key memory performance factors that can identify low memory symptoms.
- the system test method according to the present invention can identify various performance bottlenecks.
- the system test method according to the present invention may determine a memory bottleneck based on a page fault.
- a high page fault may be a memory bottleneck.
- Page faults occur when a program tries to access data or code that exists in its address space but does not currently exist in the system's memory.
- the operating system imports the data into memory so that the program continues to run as if no page fault occurred. Due to the exception handling of the page fault of the operating system, the processing time of the application is delayed and the overall system performance is affected.
- system test method may identify a performance bottleneck through memory usage.
- System memory has physical memory usage and virtual memory usage, and can be divided into heap memory usage by each process.
- the system test method according to the present invention determines the performance bottleneck based on the sum of these memory usages.
- system test method may identify a performance bottleneck through processor usage (or CPU usage).
- the system test method according to the present invention may determine that there is a bottleneck in the CPU when there is free memory while the processor usage is kept high. On the other hand, if the processor usage is high and the memory is exhausted, the performance problem may be more of a memory bottleneck than a CPU.
- the system test method according to the present invention may identify a performance bottleneck according to processor usage.
- Process usage is the execution time of the system, which means the total CPU usage minus idle time.
- the system test method according to the present invention can determine the performance bottleneck according to the user time (User Time).
- Usage time refers to the time the execution stays in user space, which means the execution time of the application.
- system test method according to the present invention may determine the performance bottleneck according to the kernel time.
- Kernel usage time is the time the execution stays in kernel space, which means the service processing time of the kernel.
- Process control blocks are data structures managed by the operating system kernel for the purpose of controlling processes at run time.
- process control blocks store execution information such as process identifiers, register contexts, process address spaces, process memory usage, shared function lists, resources owned by processes, process priorities, and states.
- FIG. 1 is a flowchart illustrating a system test method according to the present invention.
- the system test method may include identifying a location of a process control block (S100), accessing a process control block (S200), and monitoring performance factors of the process control block (S300). ).
- the position where the process control block is stored is not determined because the process control block is also generated and disappears when the process is created and disappeared.
- the process control of the current process is because the base address of the process control block for the current process that occupies the processor (e.g. CPU) is managed in a specific memory space or, in some cases, a fixed address in advance.
- the block information can be known.
- the process control block base address of the current process may be calculated as a stack pointer, and as in line 31, the process control block of all processes may be accessed.
- step S200 of accessing the location of the process control block the process control block is present in the kernel memory space.
- the pseudo code can be implemented in the form of virtual driver to share the kernel address space as shown in the following program code to access the process control block in the kernel memory space.
- the timer-interrupt may be used as in line 61 and line 65 of the program code of FIG. 2 and the performance data may be measured at a specified time interval (eg 1 sec, 100 msec). .
- the performance factor while circulating the process and thread lists of the process control block as in line 31 and line 33 of the program code of FIG. Can be measured.
- the call stack information is stored per thread to track in detail where the system performance bottleneck occurs. Performance factors measured by each monitoring unit are as follows.
- the performance factor of the process control block may include one or more of processor usage, memory usage, and page faults.
- the performance factor for the process of the process control block may include one or more of an ID, a process state, a process priority, a heap usage, a process operating time, a use time, and a kernel use time.
- Performance factors for threads in a process control block may include one or more of: ID, Run State, Default Priority, Current Priority, Usage Time, Kernel Usage Time, and Call Stack Information.
- FIG. 3 shows a structure of a system for executing a system test method according to the present invention.
- a system for executing a system test method according to the present invention includes an agent unit 120 and a test manager 210.
- the agent unit 120 is included in the target system to be tested, and performs a role of measuring performance data.
- the agent unit 120 executes the algorithm shown in FIG.
- the test management unit 210 is included in a host system 200 such as a personal computer (PC) to analyze performance data collected from the agent unit 120 to detect performance bottlenecks and analyze test coverage.
- a host system 200 such as a personal computer (PC) to analyze performance data collected from the agent unit 120 to detect performance bottlenecks and analyze test coverage.
- PC personal computer
- the agent unit 120 is mounted together with the target system disposed in the operating environment, and operates the system according to the test start and end commands of the user, and periodically measures data related to system performance.
- the agent unit 120 may include PerfAgent.dll and PerfROBO.exe.
- PerfAgent.dll is a virtual kernel device driver that implements the algorithm shown in FIG. 1 and hacks the process control block information of the kernel for performance testing.
- PerfROBO.exe acts as a test server that controls whether PerfAgent.dll is activated by user's test start and stop commands.
- the test is terminated by executing the system performance monitoring module through the timer setting and ending the set timer even when the test is terminated by the user request.
- the test manager 210 may store the collected performance data in a designated storage medium.
- the test manager 210 analyzes the log file of the host system 200 and detects a performance bottleneck occurred at an operating time.
- test management unit 210 stores the performance data as binary code in a storage medium
- the test management unit 210 inputs binary execution code and collected profiling data for a test target, and test coverage and performance.
- the location information of which function location has occurred can be displayed together with the call stack information.
- an analysis code can be inserted into the kernel. This technique inserts analytical code into the kernel either statically or dynamically.
- Dynamic insertion techniques allow you to insert analysis code into the kernel code at run-time, in which case you can insert code that gathers data for performance analysis without rebooting the system.
- the technique of static insertion uses a prebuilt kernel.
- a method using a simulator as a performance monitoring technique may be used. This is useful when looking at the performance of a system early in the development phase.
- Hardware can be used as a performance monitoring technique.
- Hardware performance elements represent a specially designed set of registers, and it is possible to monitor the performance associated with CPU, cache, and memory with less system overhead than software-based performance elements. This way, you don't have to modify the source or binary code.
- the present invention can test a system without affecting the operating environment of the system by using a minimum amount of resources required for operating the system.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Automation & Control Theory (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
Description
Claims (12)
- 프로세스 제어 블록(Process Control Block)의 위치를 식별하는 단계;상기 프로세스 제어 블록의 위치에 접근하는 단계; 및상기 프로세스 제어 블록의 성능 요소를 모니터링하는 단계를 포함하는 시스템 테스트 방법.
- 청구항 1에 있어서,상기 프로세스 제어 블록은커널 메모리 내부에 위치하는 것을 특징으로 하는 시스템 테스트 방법.
- 청구항 2에 있어서,상기 프로세스 제어 블록의 위치에 접근하는 단계에 있어서,가상 드라이버를 사용하여 상기 커널 메모리에 접근하는 것을 특징으로 하는 시스템 테스트 방법.
- 청구항 1에 있어서,상기 프로세스 제어 블록의 성능 요소를 모니터링하는 단계에 있어서,미리 설정된 시간 간격마다 상기 프로세스 제어 블록의 성능 요소를 측정하는 것을 특징으로 하는 시스템 테스트 방법.
- 청구항 2에 있어서,상기 프로세스 제어 블록의 성능 요소를 모니터링하는 단계에 있어서,상기 프로세스 제어 블록의 프로세스 및 쓰레드(Thread)에 대한 성능 요소를 측정하는 것을 특징으로 하는 시스템 테스트 방법.
- 청구항 5에 있어서,상기 프로세스 제어 블록의 성능 요소는프로세서 사용량, 메모리 사용량, 페이지 폴트(Page Fault) 중 하나 이상을 포함하는 것을 특징으로 하는 시스템 테스트 방법.
- 청구항 6에 있어서,상기 프로세스 제어 블록의 프로세스에 대한 성능 요소는아이디(ID), 프로세스의 상태, 프로세스의 우선 순위, 힙(Heap) 사용량, 프로세스의 동작 시간, 사용 시간, 커널 사용 시간 중 하나 이상을 포함하는 것을 특징으로 하는 시스템 테스트 방법.
- 청구항 6에 있어서,상기 프로세스 제어 블록의 쓰레드에 대한 성능 요소는아이디, 운영 상태(Run State), 기본 우선 순위, 현재 우선 순위, 사용 시간, 커널 사용 시간, 콜 스택(Call Stack) 중 하나 이상을 포함하는 것을 특징으로 하는 시스템 테스트 방법.
- 청구항 1에 있어서,상기 프로세스 제어 블록은프로세스의 식별자, 레지스터 컨텍스트(Context), 프로세스의 어드레스, 메모리 사용량, 공유 함수 목록, 프로세스의 자원(Resource), 프로세스의 우선 순위, 프로세스의 상태 중 하나 이상에 대한 정보를 저장하는 것을 특징으로 하는 시스템 테스트 방법.
- 청구항 1에 있어서,상기 프로세스 제어 블록의 성능 요소를 모니터링하는 단계는커널에 분석 코드를 삽입하여 상기 프로세스 제어 블록의 성능 요소를 모니터링하는 것을 특징으로 하는 시스템 테스트 방법.
- 청구항 1에 있어서,상기 프로세스 제어 블록의 성능 요소를 모니터링하는 단계는시뮬레이션 프로그램을 사용하여 상기 프로세스 제어 블록의 성능 요소를 모니터링하는 것을 특징으로 하는 시스템 테스트 방법.
- 청구항 1에 있어서,상기 프로세스 제어 블록의 성능 요소를 모니터링하는 단계는레지스터를 포함하는 하드웨어를 사용하여 상기 프로세스 제어 블록의 성능 요소를 모니터링하는 것을 특징으로 하는 시스템 테스트 방법.
Priority Applications (14)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA2800271A CA2800271A1 (en) | 2010-09-07 | 2010-09-07 | System test method |
PCT/KR2010/006068 WO2012033237A1 (ko) | 2010-09-07 | 2010-09-07 | 시스템 테스트 방법 |
CN201080067546.9A CN103109276B (zh) | 2010-09-07 | 2010-09-07 | 系统测试方法 |
KR1020127034454A KR101438990B1 (ko) | 2010-09-07 | 2010-09-07 | 시스템 테스트 방법 |
JP2013518210A JP2013533553A (ja) | 2010-09-07 | 2010-09-07 | システムテスト方法 |
EP10857024.3A EP2615552A4 (en) | 2010-09-07 | 2010-09-07 | METHOD OF SYSTEM TESTING |
EP11801042.0A EP2587379B1 (en) | 2010-06-28 | 2011-03-15 | System test apparatus |
PCT/KR2011/001803 WO2012002635A1 (ko) | 2010-06-28 | 2011-03-15 | 시스템 테스트 장치 |
JP2013518216A JP5719930B2 (ja) | 2010-06-28 | 2011-03-15 | システムテスト装置 |
KR1020127034163A KR101459867B1 (ko) | 2010-06-28 | 2011-03-15 | 시스템 테스트 장치 |
CA2802415A CA2802415C (en) | 2010-06-28 | 2011-03-15 | System test apparatus |
CN201180032537.0A CN102959519B (zh) | 2010-06-28 | 2011-03-15 | 系统测试设备 |
US13/704,490 US9354996B2 (en) | 2010-06-28 | 2011-03-15 | System test apparatus |
US13/693,136 US20130096880A1 (en) | 2010-09-07 | 2012-12-04 | System test method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/KR2010/006068 WO2012033237A1 (ko) | 2010-09-07 | 2010-09-07 | 시스템 테스트 방법 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/693,136 Continuation US20130096880A1 (en) | 2010-09-07 | 2012-12-04 | System test method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012033237A1 true WO2012033237A1 (ko) | 2012-03-15 |
Family
ID=45810821
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2010/006068 WO2012033237A1 (ko) | 2010-06-28 | 2010-09-07 | 시스템 테스트 방법 |
Country Status (7)
Country | Link |
---|---|
US (1) | US20130096880A1 (ko) |
EP (1) | EP2615552A4 (ko) |
JP (1) | JP2013533553A (ko) |
KR (1) | KR101438990B1 (ko) |
CN (1) | CN103109276B (ko) |
CA (1) | CA2800271A1 (ko) |
WO (1) | WO2012033237A1 (ko) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103914653A (zh) * | 2012-12-31 | 2014-07-09 | 现代自动车株式会社 | 用于检查软件的方法及系统 |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9354996B2 (en) | 2010-06-28 | 2016-05-31 | Hyundai Motor Company | System test apparatus |
KR101459868B1 (ko) | 2011-03-15 | 2014-11-12 | 현대자동차주식회사 | 통신 테스트 장치 및 방법 |
WO2013000494A1 (en) * | 2011-06-30 | 2013-01-03 | Telefonaktiebolaget L M Ericsson (Publ) | Flexible data communication |
US8996919B2 (en) * | 2012-03-13 | 2015-03-31 | Invensense, Inc. | Method and system providng a self-test on one or more sensors coupled to a device |
US9087041B2 (en) * | 2012-07-24 | 2015-07-21 | Michael Weir | Enterprise test system platform and associated method for interoperable test data management, test development, test libraries and test workflow management and automation |
CN105468397A (zh) * | 2014-09-11 | 2016-04-06 | 腾讯科技(深圳)有限公司 | 软件运行数据处理方法及软件运行数据处理装置 |
WO2016084150A1 (ja) * | 2014-11-26 | 2016-06-02 | 株式会社日立製作所 | サーバ計算機、計算機システム、及び、方法 |
CN104850478B (zh) * | 2014-12-19 | 2017-06-06 | 北汽福田汽车股份有限公司 | 一种建立待测对象模型的方法及虚拟测试方法 |
CN106293890B (zh) * | 2015-06-09 | 2019-11-05 | 阿里巴巴集团控股有限公司 | 一种基于复杂度的业务处理方法和装置 |
CN111488290B (zh) * | 2020-04-28 | 2021-01-22 | 南方电网数字电网研究院有限公司 | 基于智能电表操作系统的线程测试方法和装置 |
CN112306803A (zh) * | 2020-10-29 | 2021-02-02 | 金蝶云科技有限公司 | 一种性能监控方法及相关设备 |
CN114968745B (zh) * | 2022-06-10 | 2023-06-16 | 北京世冠金洋科技发展有限公司 | 一种处理系统模型的运行信息的方法及装置 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20030041612A (ko) * | 2001-11-20 | 2003-05-27 | (주)유니트시스템즈 | 서버 병목을 실시간으로 분석하는 방법 |
KR20080079343A (ko) * | 2006-12-15 | 2008-09-01 | 주식회사 케이티프리텔 | 이동통신망의 미들웨어 서버를 모니터링하는 서버 및 그방법 |
KR20090001897A (ko) * | 2007-05-29 | 2009-01-09 | 주식회사 케이티프리텔 | 턱시도 미들웨어 환경의 모니터링 시스템 및 방법 |
KR20090081749A (ko) * | 2008-01-25 | 2009-07-29 | 삼성전자주식회사 | 응용프로그램의 자원 모니터링 방법 및 그 장치 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10269110A (ja) * | 1997-03-26 | 1998-10-09 | Toshiba Corp | 計算機システムのハングアップ回避方法並びにこの方法を用いた計算機システム。 |
US6175916B1 (en) * | 1997-05-06 | 2001-01-16 | Microsoft Corporation | Common-thread inter-process function calls invoked by jumps to invalid addresses |
JP2001318805A (ja) * | 2000-05-08 | 2001-11-16 | Nec Corp | 組み込みシステムのテスト方法及びテストシステム |
US6988263B1 (en) * | 2000-07-10 | 2006-01-17 | International Business Machines Corporation | Apparatus and method for cataloging symbolic data for use in performance analysis of computer programs |
JP4562568B2 (ja) * | 2005-03-28 | 2010-10-13 | 富士通テン株式会社 | 異常検出プログラムおよび異常検出方法 |
EP1962192A1 (en) * | 2007-02-21 | 2008-08-27 | Deutsche Telekom AG | Method and system for the transparent migration of virtual machine storage |
CN101398780B (zh) * | 2007-09-27 | 2011-08-24 | 国际商业机器公司 | 可基于进程定制调试器的即时调试的方法和系统 |
US9354996B2 (en) * | 2010-06-28 | 2016-05-31 | Hyundai Motor Company | System test apparatus |
-
2010
- 2010-09-07 CA CA2800271A patent/CA2800271A1/en not_active Abandoned
- 2010-09-07 CN CN201080067546.9A patent/CN103109276B/zh active Active
- 2010-09-07 WO PCT/KR2010/006068 patent/WO2012033237A1/ko active Application Filing
- 2010-09-07 KR KR1020127034454A patent/KR101438990B1/ko active IP Right Grant
- 2010-09-07 JP JP2013518210A patent/JP2013533553A/ja active Pending
- 2010-09-07 EP EP10857024.3A patent/EP2615552A4/en not_active Ceased
-
2012
- 2012-12-04 US US13/693,136 patent/US20130096880A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20030041612A (ko) * | 2001-11-20 | 2003-05-27 | (주)유니트시스템즈 | 서버 병목을 실시간으로 분석하는 방법 |
KR20080079343A (ko) * | 2006-12-15 | 2008-09-01 | 주식회사 케이티프리텔 | 이동통신망의 미들웨어 서버를 모니터링하는 서버 및 그방법 |
KR20090001897A (ko) * | 2007-05-29 | 2009-01-09 | 주식회사 케이티프리텔 | 턱시도 미들웨어 환경의 모니터링 시스템 및 방법 |
KR20090081749A (ko) * | 2008-01-25 | 2009-07-29 | 삼성전자주식회사 | 응용프로그램의 자원 모니터링 방법 및 그 장치 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103914653A (zh) * | 2012-12-31 | 2014-07-09 | 现代自动车株式会社 | 用于检查软件的方法及系统 |
CN103914653B (zh) * | 2012-12-31 | 2018-10-02 | 现代自动车株式会社 | 用于检查软件的方法及系统 |
Also Published As
Publication number | Publication date |
---|---|
CA2800271A1 (en) | 2012-03-15 |
KR20130031860A (ko) | 2013-03-29 |
JP2013533553A (ja) | 2013-08-22 |
CN103109276A (zh) | 2013-05-15 |
EP2615552A1 (en) | 2013-07-17 |
KR101438990B1 (ko) | 2014-09-05 |
CN103109276B (zh) | 2016-01-20 |
US20130096880A1 (en) | 2013-04-18 |
EP2615552A4 (en) | 2014-08-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2012033237A1 (ko) | 시스템 테스트 방법 | |
WO2019117593A1 (ko) | 컨테이너 기반의 자원 할당을 지원하는 클라우드 컴퓨팅 장치 및 방법 | |
JP6095682B2 (ja) | プログラム・イベント記録イベントのランタイム計装イベントへの変換 | |
US9529614B2 (en) | Automatically bridging the semantic gap in machine introspection | |
US7047521B2 (en) | Dynamic instrumentation event trace system and methods | |
WO2013154365A1 (ko) | 단말기에서 태스크 스케줄링을 수행하는 방법 및 장치 | |
KR19990077480A (ko) | 데이터처리시스템및애플리케이션의구조화된프로파일링방법및장치 | |
JP6138142B2 (ja) | 被管理ランタイムのためのハードウェア・ベース・ランタイム計装機構 | |
WO2012002635A1 (ko) | 시스템 테스트 장치 | |
JP6195572B2 (ja) | ランタイム計装制御の状況の決定のためのコンピュータ・プログラム、方法、およびシステム | |
CN107066390B (zh) | 一种动态内存泄漏检测方法及系统 | |
WO2015072689A1 (ko) | 안티디버깅 방법 | |
WO2014088144A1 (ko) | 단위 테스트 케이스 재사용 기반의 함수 테스트 장치 및 그 함수 테스트 방법 | |
GB2383437A (en) | Integrated hardware treace unit | |
US20070226697A1 (en) | Autonomic performance management | |
US8875114B2 (en) | Employing identifiers provided by an operating system of a processing environment to optimize the processing environment | |
WO2013165180A1 (ko) | 로그 모니터링 방법, 그 서버 및 기록 매체 | |
US8307246B2 (en) | Real time monitoring of computer for determining speed of various processes | |
EP2690558B1 (en) | Semiconductor device | |
WO2022124720A1 (ko) | 운영체제 커널 메모리의 실시간 오류 검출 방법 | |
WO2013168947A1 (ko) | 모니터링 자원의 사용량 표현 방법, 컴퓨팅 장치 및 그 방법을 실행시키기 위한 프로그램을 기록한 기록 매체 | |
Seo et al. | A profiling method by PCB hooking and its application for memory fault detection in embedded system operational test | |
CN113076233B (zh) | 一种io性能检测方法、装置、设备及存储介质 | |
US7895581B2 (en) | Profiling collector for computer system | |
US20100153926A1 (en) | Operating system aided code coverage |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201080067546.9 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10857024 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2013518210 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2800271 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010857024 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 20127034454 Country of ref document: KR Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |