This tutorial guides you to create CarbonData Tables and optimize performance. The following sections will elaborate on the above topics :
Recently CarbonData was used to analyze performance of Telecommunication field. The results of the analysis for table creation with dimensions ranging from 10 thousand to 10 billion rows and 100 to 300 columns have been summarized below.
The following table describes some of the columns from the table used.
Table Column Description
|Column Name||Data Type||Cardinality||Attribution|
CarbonData has more than 50 test cases, on the basis of these we have following suggestions to enhance the query performance :
Put the frequently-used column filter in the beginning
For example, MSISDN filter is used in most of the query then we must put the MSISDN in the first column. The create table command can be modified as suggested below :
create table carbondata_table( msisdn String, ... )STORED BY 'org.apache.carbondata.format' TBLPROPERTIES ( 'DICTIONARY_EXCLUDE'='MSISDN,..', 'DICTIONARY_INCLUDE'='...');
Now the query with MSISDN in the filter will be more efficient.
Put the frequently-used columns in the order of low to high cardinality
If the table in the specified query has multiple columns which are frequently used to filter the results, it is suggested to put the columns in the order of cardinality low to high. This ordering of frequently used columns improves the compression ratio and enhances the performance of queries with filter on these columns.
For example if MSISDN, HOST and Dime_1 are frequently-used columns, then the column order of table is suggested as Dime_1>HOST>MSISDN as Dime_1 has the lowest cardinality. The create table command can be modified as suggested below :
create table carbondata_table( Dime_1 String, HOST String, MSISDN String, ... )STORED BY 'org.apache.carbondata.format' TBLPROPERTIES ( 'DICTIONARY_EXCLUDE'='MSISDN,HOST..', 'DICTIONARY_INCLUDE'='Dime_1..');
Put the Dimension type columns in order of low to high cardinality
If the columns used to filter are not frequently used, then it is suggested to order all the columns of dimension type in order of low to high cardinality. The create table command can be modified as below :
create table carbondata_table( Dime_1 String, BEGIN_TIME bigint, HOST String, MSISDN String, ... )STORED BY 'org.apache.carbondata.format' TBLPROPERTIES ( 'DICTIONARY_EXCLUDE'='MSISDN,HOST,IMSI..', 'DICTIONARY_INCLUDE'='Dime_1,END_TIME,BEGIN_TIME..');
For measure type columns with non high accuracy, replace Numeric(20,0) data type with Double data type
For columns of measure type, not requiring high accuracy, it is suggested to replace Numeric data type with Double to enhance query performance. The create table command can be modified as below :
create table carbondata_table( Dime_1 String, BEGIN_TIME bigint, HOST String, MSISDN String, counter_1 double, counter_2 double, ... counter_100 double )STORED BY 'org.apache.carbondata.format' TBLPROPERTIES ( 'DICTIONARY_EXCLUDE'='MSISDN,HOST,IMSI', 'DICTIONARY_INCLUDE'='Dime_1,END_TIME,BEGIN_TIME');
The result of performance analysis of test-case shows reduction in query execution time from 15 to 3 seconds, thereby improving performance by nearly 5 times.
Columns of incremental character should be re-arranged at the end of dimensions
Consider the following scenario where data is loaded each day and the begin_time is incremental for each load, it is suggested to put begin_time at the end of dimensions.
Incremental values are efficient in using min/max index. The create table command can be modified as below :
create table carbondata_table( Dime_1 String, HOST String, MSISDN String, counter_1 double, counter_2 double, BEGIN_TIME bigint, ... counter_100 double )STORED BY 'org.apache.carbondata.format' TBLPROPERTIES ( 'DICTIONARY_EXCLUDE'='MSISDN,HOST,IMSI', 'DICTIONARY_INCLUDE'='Dime_1,END_TIME,BEGIN_TIME');
Avoid adding high cardinality columns to dictionary
If the system has low memory configuration, then it is suggested to exclude high cardinality columns from the dictionary to enhance load performance. Creation of dictionary for high cardinality columns at time of load will degrade load performance due to excessive memory usage.
By default CarbonData determines the cardinality at the first data load and allows for dictionary creation only if the cardinality is less than 1 million.
CarbonData supports large data load, in this process sorting data while loading consumes a lot of memory and disk IO and this can result sometimes in "Out Of Memory" exception. If you do not have much memory to use, then you may prefer to slow the speed of data loading instead of data load failure. You can configure CarbonData by tuning following properties in carbon.properties file to get a better performance.
|carbon.number.of.cores.while.loading||Default: 2.This value should be >= 2||Specifies the number of cores used for data processing during data loading in CarbonData.|
|carbon.sort.size||Default: 100000. The value should be >= 100.||Threshold to write local file in sort step when loading data|
|carbon.sort.file.write.buffer.size||Default: 50000.||DataOutputStream buffer.|
|carbon.number.of.cores.block.sort||Default: 7||If you have huge memory and cpus, increase it as you will|
|carbon.merge.sort.reader.thread||Default: 3||Specifies the number of cores used for temp file merging during data loading in CarbonData.|
|carbon.merge.sort.prefetch||Default: true||You may want set this value to false if you have not enough memory|
For example, if there are 10 million records ,and i have only 16 cores ,64GB memory, will be loaded to CarbonData table. Using the default configuration always fail in sort step. Modify carbon.properties as suggested below:
carbon.number.of.cores.block.sort=1 carbon.merge.sort.reader.thread=1 carbon.sort.size=5000 carbon.sort.file.write.buffer.size=5000 carbon.merge.sort.prefetch=false
Recently we did some performance POC on CarbonData for Finance and telecommunication Field. It involved detailed queries and aggregation scenarios. After the completion of POC, some of the configurations impacting the performance have been identified and tabulated below :
|carbon.sort.intermediate.files.limit||spark/carbonlib/carbon.properties||Data loading||During the loading of data, local temp is used to sort the data. This number specifies the minimum number of intermediate files after which the merge sort has to be initiated.||Increasing the parameter to a higher value will improve the load performance. For example, when we increase the value from 20 to 100, it increases the data load performance from 35MB/S to more than 50MB/S. Higher values of this parameter consumes more memory during the load.|
|carbon.number.of.cores.while.loading||spark/carbonlib/carbon.properties||Data loading||Specifies the number of cores used for data processing during data loading in CarbonData.||If you have more number of CPUs, then you can increase the number of CPUs, which will increase the performance. For example if we increase the value from 2 to 4 then the CSV reading performance can increase about 1 times|
|carbon.compaction.level.threshold||spark/carbonlib/carbon.properties||Data loading and Querying||For minor compaction, specifies the number of segments to be merged in stage 1 and number of compacted segments to be merged in stage 2.||Each CarbonData load will create one segment, if every load is small in size it will generate many small file over a period of time impacting the query performance. Configuring this parameter will merge the small segment to one big segment which will sort the data and improve the performance. For Example in one telecommunication scenario, the performance improves about 2 times after minor compaction.|
|spark.sql.shuffle.partitions||spark/conf/spark-defaults.conf||Querying||The number of task started when spark shuffle.||The value can be 1 to 2 times as much as the executor cores. In an aggregation scenario, reducing the number from 200 to 32 reduced the query time from 17 to 9 seconds.|
|spark.executor.instances/spark.executor.cores/spark.executor.memory||spark/conf/spark-defaults.conf||Querying||The number of executors, CPU cores, and memory used for CarbonData query.||In the bank scenario, we provide the 4 CPUs cores and 15 GB for each executor which can get good performance. This 2 value does not mean more the better. It needs to be configured properly in case of limited resources. For example, In the bank scenario, it has enough CPU 32 cores each node but less memory 64 GB each node. So we cannot give more CPU but less memory. For example, when 4 cores and 12GB for each executor. It sometimes happens GC during the query which impact the query performance very much from the 3 second to more than 15 seconds. In this scenario need to increase the memory or decrease the CPU cores.|
|carbon.detail.batch.size||spark/carbonlib/carbon.properties||Data loading||The buffer size to store records, returned from the block scan.||In limit scenario this parameter is very important. For example your query limit is 1000. But if we set this value to 3000 that means we get 3000 records from scan but spark will only take 1000 rows. So the 2000 remaining are useless. In one Finance test case after we set it to 100, in the limit 1000 scenario the performance increase about 2 times in comparison to if we set this value to 12000.|
|carbon.use.local.dir||spark/carbonlib/carbon.properties||Data loading||Whether use YARN local directories for multi-table load disk load balance||If this is set it to true CarbonData will use YARN local directories for multi-table load disk load balance, that will improve the data load performance.|
Note: If your CarbonData instance is provided only for query, you may specify the property 'spark.speculation=true' which is in conf directory of spark.