Volatile Memory Log Data Mediator for I/O Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The frequent input and output operations on non-volatile memory devices for accessing log data by multiple services lead to inefficient use of computational resources and performance delays, especially during high traffic or frequent access times.
Innovation Solution
Storing log data in volatile memory and using a file system to manage access by multiple services, with a daemon controlling access based on priority and device data to optimize data transfer rates and resource utilization, thereby reducing the need for disk I/O operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If log data is stored in non-volatile memory and accessed by multiple services, then data persistence and reliability are improved, but I/O operation overhead and computational resource consumption increase
Solution Approach 1:
The patent introduces volatile memory as an intermediary layer between non-volatile memory and multiple services. Log data is first written to volatile memory by a single service, then multiple services can access it without direct disk I/O operations. This mediator resolves the contradiction by maintaining data accessibility (reliability) while eliminating repeated I/O operations (productivity improvement).
Solution Approach 2:
The system performs preliminary action by pre-loading log data into volatile memory before multiple services need to access it. The first service writes data to volatile memory in advance, so subsequent services can access it quickly without performing I/O operations. This preliminary storage action resolves the efficiency problem while maintaining data availability.
2Adaptability or versatility
If multiple services access log data frequently, then service functionality and data utilization are improved, but disk I/O operations and time consumption increase
Solution Approach 1:
Volatile memory serves as a mediator that enables multiple services to access log data rapidly without time-consuming disk I/O operations. The intermediary layer provides fast read access to all services simultaneously, resolving the contradiction between versatile access capability and time consumption.
Solution Approach 2:
The system creates a copy of log data in volatile memory that can be accessed by multiple services without reading from the original disk location repeatedly. This copying mechanism allows unlimited service access without proportional increase in I/O operations, eliminating the time loss contradiction.
3Reliability
If log data is written to disk for each service access, then data availability is ensured, but computational resource overhead and processing delays increase
Solution Approach 1:
Volatile memory acts as an intermediary that decouples data availability from computational resource consumption. Once data is in volatile memory, multiple services can access it with minimal energy expenditure, eliminating the need for repeated high-energy disk I/O operations while maintaining data availability.
Solution Approach 2:
The volatile memory layer enables services to self-serve data without requiring disk I/O operations for each access. Services can directly read from the already-loaded data in volatile memory, reducing computational overhead and energy consumption while maintaining continuous data availability.
Data Source
AI summary
To reduce the time, cost, and computational resources associated with writing to and reading from a non-volatile memory device multiple times, log data is stored in volatile memory of a computing device. The host device includes a file system that receives the log data from an application when the application sends an instruction to write the log data to the file system. Once the log data is stored in volatile memory, device data indicative of the rate at which log data is received by and transmitted from the computing device, and an amount of unused memory or other computational resources of the computing device, may be used to determine which services are permitted to access the log data, and whether to provide access to all of the log data or only a portion of the log data based on a sampling rate.