ID | IEP-22 | ||||||||
Author | Vladimir Ozerov Ozerov | ||||||||
Sponsor | Vladimir Ozerov Ozerov | ||||||||
Created | 15 Jun 2018 | ||||||||
Status |
|
Table of Contents |
---|
Initial data load is one of the most frequent and important use cases for Apache Ignite. At the moment the fastest way to load data is data streamer, which relies on asynchronous messaging and fast-path entry update method [1]. But all other internal mechanics of cache and page memory works as usual during data load.
General approach employed by major database vendors is to disable and/or skip as much internals as possible during data load, and to employ alternative sorting methods for indexes. With this idea in mind, we have potential to improve data loading speed in several times as follows:
Speedup is expected from less number of IO operations and and less locking page/entry overhead.
Most industrial vendors rely on the following assumptions:
Oracle offers "direct path load" [1] as the fastest method to populate data. Direct path load can be from both command line utility SQL*Loader to load existing files (resembling Ignite's COPY command), and with conventional SQL, such as {{INSERT}} and {{CREATE TABLE AS SELECT}} (CTAS).
[1] https://docs.oracle.com/cd/E11882_01/server.112/e22490/ldr_modes.htm#SUTIL009
[2] https://docs.oracle.com/en/database/oracle/oracle-database/18/admin/managing-tables.html#GUID-134D6EB6-219E-4820-AB54-8C60067A8F0F
TODO
TODO
TODO
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|