Blockchain Ledger Compression Allocation for Faster Data Writing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Centralized blockchain-type ledgers experience low efficiency when storing large volumes of data, such as reports or multimedia files, due to inefficient data writing processes.
Innovation Solution
A data storage method that dynamically assesses hardware and network specifications of a client to determine whether to perform data compression locally or on a database server, optimizing compression based on these specifications to improve writing efficiency in the ledger.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If original files are written into the ledger without compression, then data integrity is maintained, but writing efficiency is too low
Solution Approach 1:
The patent applies preliminary action by performing data compression before writing data into the blockchain ledger. The client or database server compresses the data in advance, reducing the volume of data that needs to be written to the ledger, thereby improving writing efficiency and reducing the time required for data storage operations.
2Volume of stationary object
If data compression is performed, then ledger occupation space is reduced, but system complexity increases
Solution Approach 1:
The patent applies local quality by making the compression function distributed between different components of the system. The client can perform compression locally based on its hardware capabilities, or the database server can perform compression. This distributes the complexity rather than concentrating it in one location, and allows each component to handle compression only when appropriate to its capabilities.
Solution Approach 2:
The patent applies dynamics by making the compression decision dynamic rather than static. The system evaluates hardware specifications and network environment specifications to dynamically determine whether compression should be performed and by which component. This dynamic approach allows the system to adapt to different conditions and optimize performance accordingly.
3Speed
If compression is performed based on hardware specifications, then writing speed is improved, but energy consumption increases
Solution Approach 1:
The patent applies parameter changes by using hardware specifications and network environment specifications as parameters to determine the compression strategy. The system evaluates parameters such as CPU performance, memory availability, and network conditions to decide whether to perform compression and by which component, thereby optimizing the balance between writing speed and energy consumption based on the specific operational context.
Data Source
AI summary
This disclosure relates to data storage in a blockchain-type ledger storing data based on a blockchain data structure. In one aspect, a method includes obtaining service data. A compression threshold on which selection of a target object for performing data compression is based is determined. The target object includes a client device or a database server. At least one of a hardware performance parameter or a network performance parameter is obtained. A compression weight is determined based on at least one of the hardware performance parameter or the network performance parameter. When the compression weight is greater than a predetermined value, data compression is performed on the service data at the client device. When the compression weight is less than or equal to the predetermined value, the client device sends the service data to the database server so that the database server performs data compression on the service data.