CN117762906B - Redis-based cold and hot data separation method and system - Google Patents

Redis-based cold and hot data separation method and system Download PDF

Info

Publication number
CN117762906B
CN117762906B CN202410195765.9A CN202410195765A CN117762906B CN 117762906 B CN117762906 B CN 117762906B CN 202410195765 A CN202410195765 A CN 202410195765A CN 117762906 B CN117762906 B CN 117762906B
Authority
CN
China
Prior art keywords
data
cold
database
memory
redis
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202410195765.9A
Other languages
Chinese (zh)
Other versions
CN117762906A (en
Inventor
夏海峰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Ling Skylark Technology Co ltd
Original Assignee
Beijing Ling Skylark Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Ling Skylark Technology Co ltd filed Critical Beijing Ling Skylark Technology Co ltd
Priority to CN202410195765.9A priority Critical patent/CN117762906B/en
Publication of CN117762906A publication Critical patent/CN117762906A/en
Application granted granted Critical
Publication of CN117762906B publication Critical patent/CN117762906B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The embodiment of the invention discloses a cold and hot data separation method and a system based on Redis, and the embodiment of the invention comprises the following steps: s1, introducing a Redis Module expansion function according to a Redis database; s2, storing cold data into an integratable embedded database, and setting the integratable embedded database as a cold data storage library; s3, judging whether the current memory state reaches a preset threshold value of the maximum memory, if so, starting to expel the memory to perform data migration, and if not, not performing data migration; and S4, marking each cold data by using a Cuckoo filter, and inquiring whether a Key is the cold data or not by using the Cuckoo filter. The embodiment of the invention uses the Redis Module plug-in, ensures the compatibility of the service with the existing client to the greatest extent, realizes an embedded cold and hot data separation mode, breaks through the limitation of the memory for the data storage size of the Redis, improves the reliability of the service, simplifies the maintenance cost and reduces the complexity of service butt joint.

Description

Redis-based cold and hot data separation method and system
Technical Field
The embodiment of the invention relates to the technical field of data separation, in particular to a cold and hot data separation method and system based on Redis.
Background
Redis is a high performance key pair storage database written using ANSI C that supports network access. It stores data based on memory and provides distributed deployment and optional persistence functionality.
Because Redis is based on memory storage, the size of the memory directly determines the data quantity which can be stored by Redis, and most of the time, the data stored in the Redis memory cannot be accessed in real time, or some data is accessed once a day or a month only for one hour, and the data is resident in the memory, so that the memory is wasted, and the traffic which can be supported by Redis is limited.
At present, cold-hot separation of data is mainly realized by two methods:
1) CN108319654 a-computing system, cold and hot data separation method and apparatus, computer readable storage medium, the patent introducing multiple roles: a first database (Redis), a second database (MySQL), a full data transfer component, a cold business data elimination component, and a data recovery component. The full-volume data transfer component realizes data transfer to a second database through Kafka; the cold service data elimination component periodically checks whether service data which is not accessed in a preset fixed time exists, and if so, deletes the service data as the cold service data. The data recovery component is configured to read the desired data from the disk and import it to the Redis memory.
2) CN 108197289B-a data storage structure, a data storage query method, a terminal and a medium, the patent has very deep service characteristics: there are two roles, one Redis as an in-memory database for storing hot data and one hard disk for storing cold data. When the service is requested, the hot data cluster is firstly inquired, and if the hot data cluster is not found, the cold data cluster is requested. The access time of each Key is recorded, and when the threshold T time is not accessed again, the Key is deleted from the hot data as cold data. This requires the service to implement this logic, coupled with the service depth.
The above method has the following disadvantages: the data storage mode in the scheme 1) is strictly limited on the service data storage mode, so that great inflexibility is caused, and meanwhile, each value is added with a score value for recording access time, so that the occupied space is large; scheme 2) the other pair of kv records is limited to be used for judging whether to delete the data according to the set elimination time T, and although the size of Key is optimized through CRC32, the two methods have the conditions of occupying a large amount of memory space additionally and having data redundancy, and have poor data access performance and single cold data definition logic.
Disclosure of Invention
Therefore, the embodiment of the invention provides a cold and hot data separation method and a cold and hot data separation system based on Redis, which are used for solving the technical problems that the prior art occupies a large amount of memory space, has data redundancy, and is poor in data access performance and single in cold data definition logic.
In order to achieve the above object, the embodiment of the present invention provides the following technical solutions:
According to a first aspect of an embodiment of the present invention, there is provided a method for separating cold and hot data based on Redis, the method including:
s1, introducing a Redis Module expansion function according to a Redis database;
S2, storing cold data into an integratable embedded database, and setting the integratable embedded database as a cold data storage library;
S3, judging whether the current memory state reaches a preset threshold value of the maximum memory, if so, starting to expel the memory to perform data migration, and if not, not performing data migration;
And S4, marking each cold data by using a Cuckoo filter, and inquiring whether a Key is the cold data or not by using the Cuckoo filter.
Further, the integrable embedded database is LevelDB or RocksDB.
Further, the LRU algorithm or the LFU algorithm is used for realizing the separation of the cold and hot data of the memory.
Further, when the user writes data at the client, it includes:
The data is directly written into the hot data memory through a Redis Module;
When a client accesses data:
inquiring a thermal database, and directly returning a result if current data exists in the thermal database;
if the current data does not exist, inquiring a Cuckoo filter to confirm whether the current data exists in the Cuckoo filter, and if the current data does not exist, returning an empty result;
if so, querying a cold database and saving the result to a hot database and returning;
and simultaneously adding the Key of the cold data into a queue to be processed to wait for asynchronous deletion from the cold database and the Cuckoo filter.
Further, when the write/access of the Key occurs, the method includes:
marking the access time and the access times of Key;
When the memory reaches a preset threshold value of the maximum memory, starting the expelling of cold data:
adding the Key to a queue to be migrated of the memory and reading the queue to be migrated by the asynchronous thread;
Writing the data into a cold database while marking the current data at a Cuckoo filter;
The current data and corresponding values are deleted from the hot database.
According to a second aspect of an embodiment of the present invention, there is provided a Redis-based cold and hot data separation system, the system including:
the extended function introduction Module is used for introducing a Redis Module extended function according to the Redis database;
The cold data storage module is used for storing cold data into an integratable embedded database and setting the integratable embedded database as a cold data storage library;
The memory judging module is used for judging whether the current memory state reaches a preset threshold value of the maximum memory, if so, starting to expel the memory to perform data migration, and if not, not performing data migration;
and the marking module is used for marking each cold data by using the Cuckoo filter and inquiring whether one Key is the cold data or not by using the Cuckoo filter.
Further, the system further comprises: the query module is used for executing the following steps:
The data is directly written into the hot data memory through a Redis Module;
inquiring whether the current data is in a Cuckoo filter, if so, deleting the current data from the cold data, and deleting a mark from the Cuckoo filter;
When a client accesses data:
inquiring a thermal database, and directly returning a result if current data exists in the thermal database;
if the current data does not exist, inquiring a Cuckoo filter to confirm whether the current data exists in the Cuckoo filter, and if the current data does not exist, returning an empty result;
if so, querying a cold database and saving the result to a hot database and returning;
and simultaneously adding the Key of the cold data into a queue to be processed to wait for asynchronous deletion from the cold database and the Cuckoo filter.
Further, the system further comprises: a write/access module for performing the steps of:
marking the access time and the access times of Key;
When the memory reaches a preset threshold value of the maximum memory, starting the expelling of cold data:
adding the Key to a queue to be migrated of the memory and reading the queue to be migrated by the asynchronous thread;
Writing the data into a cold database while marking the current data at a Cuckoo filter;
The current data and corresponding values are deleted from the hot database.
The embodiment of the invention has the following advantages:
The embodiment of the invention comprises the following steps: s1, introducing a Redis Module expansion function according to a Redis database; s2, storing cold data into an integratable embedded database, and setting the integratable embedded database as a cold data storage library; s3, judging whether the current memory state reaches a preset threshold value of the maximum memory, if so, starting to expel the memory to perform data migration, and if not, not performing data migration; and S4, marking each cold data by using a Cuckoo filter, and inquiring whether a Key is the cold data or not by using the Cuckoo filter. The embodiment of the invention uses the Redis Module plug-in, ensures the compatibility of the service with the existing client to the greatest extent, realizes an embedded cold and hot data separation mode, breaks through the limitation of the memory for the data storage size of the Redis, improves the reliability of the service, simplifies the maintenance cost and reduces the complexity of service butt joint.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It will be apparent to those of ordinary skill in the art that the drawings in the following description are exemplary only and that other implementations can be obtained from the extensions of the drawings provided without inventive effort.
The structures, proportions, sizes, etc. shown in the present specification are shown only for the purposes of illustration and description, and are not intended to limit the scope of the invention, which is defined by the claims, so that any structural modifications, changes in proportions, or adjustments of sizes, which do not affect the efficacy or the achievement of the present invention, should fall within the ambit of the technical disclosure.
Fig. 1 is a schematic logic structure diagram of a cold and hot data separation system based on Redis according to an embodiment of the present invention;
fig. 2 is a schematic diagram of an application principle of a Redis-based cold and hot data separation system according to an embodiment of the present invention;
FIG. 3 is a schematic flow chart of a Redis-based cold and hot data separation method according to an embodiment of the present invention;
Fig. 4 is a schematic flow chart of allocating time-frequency resources in a cold-hot data separation method based on Redis according to an embodiment of the present invention.
Detailed Description
Other advantages and advantages of the present invention will become apparent to those skilled in the art from the following detailed description, which, by way of illustration, is to be read in connection with certain specific embodiments, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
At present, cold-hot separation of data is mainly realized by two methods:
1) CN108319654 a-computing system, cold and hot data separation method and apparatus, computer readable storage medium, the patent introducing multiple roles: a first database (Redis), a second database (MySQL), a full data transfer component, a cold business data elimination component, and a data recovery component. The full-volume data transfer component realizes data transfer to a second database through Kafka; the cold service data elimination component periodically checks whether service data which is not accessed in a preset fixed time exists, and if so, deletes the service data as the cold service data. The data recovery component is configured to read the desired data from the disk and import it to the Redis memory.
2) CN 108197289B-a data storage structure, a data storage query method, a terminal and a medium, the patent has very deep service characteristics: there are two roles, one Redis as an in-memory database for storing hot data and one hard disk for storing cold data. When the service is requested, the hot data cluster is firstly inquired, and if the hot data cluster is not found, the cold data cluster is requested. The access time of each Key is recorded, and when the threshold T time is not accessed again, the Key is deleted from the hot data as cold data. This requires the service to implement this logic, coupled with the service depth.
The above method has the following disadvantages: the data storage mode in the scheme 1) severely limits the service data storage mode, so that great inflexibility is caused, meanwhile, each value is added with one score for recording access time, and the occupied space is large; scheme 2) use and limit to use another pair of Key-Value records first access time, is used for judging whether to delete the data according to the set elimination time T, and although the size of Key is optimized through CRC32, the two modes have the conditions of occupying a large amount of memory space additionally and data redundancy, and the technical problems that the data access performance is poor, and the cold data definition logic is single so as to solve the limitation that the radar interference avoiding mode through passive resistance cannot ensure that the interference effect is good or bad are solved.
Referring to fig. 1, an embodiment of the present invention discloses a Redis-based cold and hot data separation system, which includes: an extended function introduction module 1; a cold data storage module 2; a memory judgment module 3; a marking module 4.
Further, the system further comprises: a query module 5, configured to perform the following steps: the data is directly written into the hot data memory through a Redis Module; inquiring whether the current data is in a Cuckoo filter, if so, deleting the current data from the cold data, and deleting a mark from the Cuckoo filter; when a client accesses data: inquiring a thermal database, and directly returning a result if current data exists in the thermal database; if the current data does not exist, inquiring a Cuckoo filter to confirm whether the current data exists in the Cuckoo filter, and if the current data does not exist, returning an empty result; if so, querying a cold database and saving the result to a hot database and returning; and simultaneously adding the Key of the cold data into a queue to be processed to wait for asynchronous deletion from the cold database and the Cuckoo filter.
Further, the system further comprises: a write/access module 6 for performing the steps of: marking the access time and the access times of Key; when the memory reaches 80% of the maximum memory setting, an eviction of cold data is initiated: adding the Key to a queue to be migrated of the memory and reading the queue to be migrated by the asynchronous thread; writing the data into a cold database while marking the current data at a Cuckoo filter; the current data and corresponding values are deleted from the hot database.
Corresponding to the above-disclosed cold and hot data separation system based on Redis, the embodiment of the invention also discloses a cold and hot data separation method based on Redis. The following describes a cold and hot data separation method based on Redis in detail in conjunction with a cold and hot data separation system based on Redis described above.
Referring to fig. 2, the invention discloses a cold and hot data separation method based on Redis, and provides a cold and hot data separation method based on Redis, which comprises the following steps: s1, introducing a Redis Module expansion function according to a Redis database; s2, storing cold data into an integratable embedded database, and setting the integratable embedded database as a cold data storage library; s3, judging whether the current memory state reaches a preset threshold value of the maximum memory, if so, starting to expel the memory to perform data migration, and if not, not performing data migration; and S4, marking each cold data by using a Cuckoo filter, and inquiring whether a Key is the cold data or not by using the Cuckoo filter.
Wherein, one preferable data of the preset threshold value is 80%, and the threshold value can be set according to the actual use condition.
Further, the integrable embedded database is LevelDB or RocksDB.
Further, the LRU algorithm or the LFU algorithm is used for realizing the separation of the cold and hot data of the memory.
Further, when the user writes data at the client, it includes: the data is directly written into the hot data memory through a Redis Module; inquiring whether the current data is in a Cuckoo filter, if so, deleting the current data from the cold data, and deleting a mark from the Cuckoo filter; referring to fig. 3, when a client accesses data: inquiring a thermal database, and directly returning a result if current data exists in the thermal database; if the current data does not exist, inquiring a Cuckoo filter to confirm whether the current data exists in the Cuckoo filter, and if the current data does not exist, returning an empty result; if so, querying a cold database and saving the result to a hot database and returning; and simultaneously adding the Key of the cold data into a queue to be processed to wait for asynchronous deletion from the cold database and the Cuckoo filter.
Further, when the write/access of the Key occurs, the method includes: marking the access time and the access times of Key; when the memory reaches the threshold set by the maximum memory, referring to FIG. 4, an eviction of cold data is initiated: adding the Key to a queue to be migrated of the memory and reading the queue to be migrated by the asynchronous thread; writing the data into a cold database while marking the current data at a Cuckoo filter; the current data and corresponding values are deleted from the hot database.
When the maintenance is deployed, the maintenance can be realized by only deploying one Redis plug-in without depending on external components, thereby greatly improving the reliability of the service and simplifying the maintenance cost. The existing client is compatible through the form of the Redis plug-in, and the architecture of the Redis plug-in is compatible, so that additional customized service logic is not needed, and the complexity of service docking is reduced.
The memory is not enough, and only when the memory is insufficient, the cold data is started to be evicted, so that the service access performance is guaranteed to the greatest extent. Meanwhile, whether cold data exist or not is judged in advance by means of a Cuckoo filter, cold data access based on a hard disk is reduced, and performance is further improved.
The hot data ensures the data reliability by using the persistence function of Redis, and the cold data is stored through a hard disk, so that the cold data has reliability. Meanwhile, hot data is not stored in the cold data, so that occupation of hard disk storage is reduced, and waste of resources is reduced. Because the reliability of the Redis is multiplexed, the Redis can quickly reenter data after restarting, and the data does not need to be transferred into the Redis through hot loading or a full data transfer assembly, so that the recovery speed of hot data is accelerated.
While the invention has been described in detail in the foregoing general description and specific examples, it will be apparent to those skilled in the art that modifications and improvements can be made thereto. Accordingly, such modifications or improvements may be made without departing from the spirit of the invention and are intended to be within the scope of the invention as claimed.

Claims (4)

1. A method for separating cold and hot data based on Redis, the method comprising:
s1, introducing a Redis Module expansion function according to a Redis database;
S2, storing cold data into an integratable embedded database, and setting the integratable embedded database as a cold data storage library;
S3, judging whether the current memory state reaches a preset threshold value of the maximum memory, if so, starting to expel the memory to perform data migration, and if not, not performing data migration;
S4, marking each cold data by using a Cuckoo filter, and inquiring whether a Key is the cold data or not by using the Cuckoo filter;
The integrable embedded database is LevelDB or RocksDB;
The LRU algorithm or the LFU algorithm is used for realizing the separation of the cold and hot data of the memory;
When a user writes data at a client, the method comprises the following steps:
The data is directly written into the hot data memory through a Redis Module;
Asynchronously inquiring whether the current data is in a Cuckoo filter, if so, deleting the current data from the cold data, and deleting a mark from the Cuckoo filter;
When a client accesses data:
inquiring a thermal database, and directly returning a result if current data exists in the thermal database;
if the current data does not exist, inquiring a Cuckoo filter to confirm whether the current data exists in the Cuckoo filter, and if the current data does not exist, returning an empty result;
if so, querying a cold database and saving the result to a hot database and returning;
and simultaneously adding the Key of the cold data into a queue to be processed to wait for asynchronous deletion from the cold database and the Cuckoo filter.
2. The method for separating cold and hot data based on Redis according to claim 1, wherein when Key writing/accessing occurs, the method comprises the steps of:
marking the access time and the access times of Key;
when the memory reaches 80% of the maximum memory setting, an eviction of cold data is initiated:
adding the Key to a queue to be migrated of the memory and reading the queue to be migrated by the asynchronous thread;
Writing the data into a cold database while marking the current data at a Cuckoo filter;
The current data and corresponding values are deleted from the hot database.
3. A separation system of a Redis-based cold and hot data separation method according to claim 1 or 2, characterized in that the system comprises:
the extended function introduction Module is used for introducing a Redis Module extended function according to the Redis database;
The cold data storage module is used for storing cold data into an integratable embedded database and setting the integratable embedded database as a cold data storage library;
The memory judging module is used for judging whether the current memory state reaches 80% of the maximum memory setting, if so, starting to expel the memory for data migration, and if not, not performing data migration;
The marking module is used for marking each cold data by using a Cuckoo filter, and inquiring whether one Key is the cold data or not by the Cuckoo filter;
The system further comprises: the query module is used for executing the following steps:
The data is directly written into the hot data memory through a Redis Module;
inquiring whether the current data is in a Cuckoo filter, if so, deleting the current data from the cold data, and deleting a mark from the Cuckoo filter;
When a client accesses data:
inquiring a thermal database, and directly returning a result if current data exists in the thermal database;
if the current data does not exist, inquiring a Cuckoo filter to confirm whether the current data exists in the Cuckoo filter, and if the current data does not exist, returning an empty result;
if so, querying a cold database and saving the result to a hot database and returning;
and simultaneously adding the Key of the cold data into a queue to be processed to wait for asynchronous deletion from the cold database and the Cuckoo filter.
4. A dis-based cold and hot data separation system according to claim 3, further comprising: a write/access module for performing the steps of:
marking the access time and the access times of Key;
When the memory reaches a preset threshold value of the maximum memory, starting the expelling of cold data:
adding the Key to a queue to be migrated of the memory and reading the queue to be migrated by the asynchronous thread;
Writing the data into a cold database while marking the current data at a Cuckoo filter;
The current data and corresponding values are deleted from the hot database.
CN202410195765.9A 2024-02-22 2024-02-22 Redis-based cold and hot data separation method and system Active CN117762906B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202410195765.9A CN117762906B (en) 2024-02-22 2024-02-22 Redis-based cold and hot data separation method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202410195765.9A CN117762906B (en) 2024-02-22 2024-02-22 Redis-based cold and hot data separation method and system

Publications (2)

Publication Number Publication Date
CN117762906A CN117762906A (en) 2024-03-26
CN117762906B true CN117762906B (en) 2024-05-03

Family

ID=90318729

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202410195765.9A Active CN117762906B (en) 2024-02-22 2024-02-22 Redis-based cold and hot data separation method and system

Country Status (1)

Country Link
CN (1) CN117762906B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103473272A (en) * 2013-08-20 2013-12-25 小米科技有限责任公司 Data processing method, device and system
CN108829341A (en) * 2018-05-03 2018-11-16 上海科技大学 A kind of data managing method based on mixing storage system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109491618A (en) * 2018-11-20 2019-03-19 上海科技大学 Data management system, method, terminal and medium based on mixing storage
US11829636B2 (en) * 2021-09-01 2023-11-28 Micron Technology, Inc. Cold data identification

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103473272A (en) * 2013-08-20 2013-12-25 小米科技有限责任公司 Data processing method, device and system
CN108829341A (en) * 2018-05-03 2018-11-16 上海科技大学 A kind of data managing method based on mixing storage system

Also Published As

Publication number Publication date
CN117762906A (en) 2024-03-26

Similar Documents

Publication Publication Date Title
CN103186350B (en) The moving method of mixing storage system and hot spot data block
US8694563B1 (en) Space recovery for thin-provisioned storage volumes
CN103838853B (en) Mixed file system based on different storage media
CN102117248A (en) Caching system and method for caching data in caching system
US11314689B2 (en) Method, apparatus, and computer program product for indexing a file
CN108628542B (en) File merging method and controller
CN108089825B (en) Storage system based on distributed cluster
CN114281762B (en) Log storage acceleration method, device, equipment and medium
CN108733306A (en) A kind of Piece file mergence method and device
CN113360098A (en) Data writing method, device and system, electronic equipment and storage medium
CN114356877A (en) Log structure merged tree hierarchical storage method and system based on persistent memory
CN111159176A (en) Method and system for storing and reading mass stream data
CN115794669A (en) Method, device and related equipment for expanding memory
CN110515550A (en) A kind of method and device thereof of the cold and hot data separating of SATA solid state hard disk
CN100580669C (en) Method for realizing cache memory relates to file allocation table on Flash storage medium
CN104158863A (en) Cloud storage mechanism based on transaction-level whole-course high-speed buffer
CN112347044B (en) Object storage optimization method based on SPDK
KR100907477B1 (en) Apparatus and method for managing index of data stored in flash memory
US20240020014A1 (en) Method for Writing Data to Solid-State Drive
CN117472285A (en) Intelligent operation acceleration method for solid state disk, computer equipment and storage medium
CN116431080B (en) Data disc-dropping method, system, equipment and computer readable storage medium
CN117762906B (en) Redis-based cold and hot data separation method and system
CN115203079A (en) Method for writing data into solid state disk
US6532513B1 (en) Information recording and reproduction apparatus
CN115168317B (en) LSM tree storage engine construction method and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant