Browse Prior Art Database

Performance Profiling with Buoy Data Packets

IP.com Disclosure Number: IPCOM000234131D
Publication Date: 2014-Jan-14
Document File: 2 page(s) / 60K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed a method for performance profiling of data flow with specific "Buoy Data Packets" among computer subsystems.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 64% of the total text.

Page 01 of 2

Performance Profiling with Buoy Data Packets

For performance profiling of a computer system, it is often required to check the performance of the data flow among subsystems. To understand the data flow performance further, the questions would be like: What are the subsystems involved during the data transmission? How much time spent on each point of the data path?

Current profiling mechanism with debug messages or logs can be enabled and monitored for specific component or subsystem. However, there are problems with the current approach: 1. Not easy way to see where the data packet is flowing since all data look similar. 2. Profiling mechanism and information are scattered through out various subsystems and hard to put together the whole picture 3. Massive amount of data involved: much resource consumed if profiler is enabled for every data packet; large data logs are collected and difficult to analyze.

Disclosed is a method for performance profiling of data flow with specific "Buoy Data Packets" among computer subsystems. Specific buoy data packets are attached to the real data packets and flows along with the real data for performance monitoring. The buoy is released to the "sea" of data packet as needed to monitor the data flow.

When a buoy data packet is received by a subsystem, time stamps and other performance data are collected along with the buoy data packet. The buoy data packet flows to the next subsystem and continue the data collection at next stop....