The IQ application will be briefly unavailable on Sunday, March 31st, starting at 10:00am ET. Access will be restored as quickly as possible.
Browse Prior Art Database

A Background Process Saves Trace Data In Nonvolatile Storage

IP.com Disclosure Number: IPCOM000030086D
Original Publication Date: 2004-Jul-27
Included in the Prior Art Database: 2004-Jul-27
Document File: 2 page(s) / 32K

Publishing Venue



A high speed trace logging function and a slower archiving function work together to collect and secure computer trace data. Trace data is collected at real time speeds while a separate background process saves it in nonvolatile storage to secure it in the event of power cycling or reboot.

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

Page 1 of 2

A Background Process Saves Trace Data In Nonvolatile Storage

Trace logs are frequently produced by computer software to aid in system debugging. It is desirable to keep the logs in volatile RAM (Random Access Memory) rather than NVRAM (Non Volatile Random Access Memory) as volatile RAM is much faster. The problem is that data in RAM is usually lost upon power cycling or rebooting and unavailable when it is most needed.

While there are methods that take dumps at strategic times and save them in persistent or nonvolatile storage, the present invention describes a dual speed process that constantly saves high speed trace data in nonvolatile storage. The process is comprised of two elements.




A high speed trace logging function continuously logs trace data into a circular

RAM buffer.

A slower background process continuously monitors the content of the trace log

and archives any new data into a nonvolatile storage area.

The advantage of this method is that trace logging is not slowed by using slower NVRAM but the second process copies the data to NVRAM to make it available even in the event of power cycling or rebooting.

The trace logger is a standard circular buffer manager and runs at maximum speed since it deals only with RAM. The process that performs archiving is forced to run slower since it writes to NVRAM, but it can keep pace with the logger provided that even though the logger can run quickly in bursts, its average rate of data logging doesn't exceed...