You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@iotdb.apache.org by GitBox <gi...@apache.org> on 2020/05/10 01:45:20 UTC

[GitHub] [incubator-iotdb] qiaojialin commented on a change in pull request #1174: Concurrently write time partition

qiaojialin commented on a change in pull request #1174:
URL: https://github.com/apache/incubator-iotdb/pull/1174#discussion_r422570076



##########
File path: server/src/main/java/org/apache/iotdb/db/conf/adapter/IoTDBConfigDynamicAdapter.java
##########
@@ -30,86 +30,70 @@
  * This class is to dynamically adjust some important parameters of the system, determine the speed
  * of MenTable brushing disk, the speed of file sealing and so on, with the continuous change of
  * load in the process of system operation.
- *
+ * <p>
  * There are three dynamically adjustable parameters: maxMemTableNum, memtableSize and
  * tsFileSizeThreshold.
- *
+ * <p>
  * 1. maxMemTableNum. This parameter represents the size of the MemTable available in the MemTable
  * pool, which is closely related to the number of storage groups. When adding or deleting a storage
  * group, the parameter also adds or deletes four MemTables. The reason why adding or deleting four
  * MemTables is that when the system is running stably, the speed of the flush operation is faster
  * than that of data writing, so one is used for the Flush process and the other is used for data
  * writing. Otherwise, the system should limit the speed of data writing to maintain stability. And
  * two for sequence data, two for unsequence data.
- *
+ * <p>
  * 2. memtableSize. This parameter determines the threshold value for the MemTable in memory to be
  * flushed into disk. When the system load increases, the parameter should be set smaller so that
  * the data in memory can be flushed into disk as soon as possible.
- *
+ * <p>
  * 3. tsFileSizeThreshold. This parameter determines the speed of the tsfile seal, and then
  * determines the maximum size of metadata information maintained in memory. When the system load
  * increases, the parameter should be smaller to seal the file as soon as possible, release the
  * memory occupied by the corresponding metadata information as soon as possible.
- *
+ * <p>
  * The following equation is used to adjust the dynamic parameters of the data:
- *
- * Abbreviation of parameters:
- * 1 memtableSize: m
- * 2 maxMemTableNum: Nm
- * 3 maxSeriesNumberAmongStorageGroup: Ns
- * 4 tsFileSizeThreshold: Sf
- * 5 CompressionRatio: c
- * 6 chunk metadata size: a
- * 7 static memory: b
- * 8 allocate memory for write: S
- *
- * The equation: m * Nm + Nm * Ns * Sf * a * c / m + b = S
- * Namely: MemTable data memory size + chunk metadata memory size + static memory size = memory size for write
- *
+ * <p>
+ * Abbreviation of parameters: 1 memtableSize: m 2 maxMemTableNum: Nm 3
+ * maxSeriesNumberAmongStorageGroup: Ns 4 tsFileSizeThreshold: Sf 5 CompressionRatio: c 6 chunk
+ * metadata size: a 7 static memory: b 8 allocate memory for write: S
+ * <p>
+ * The equation: m * Nm + Nm * Ns * Sf * a * c / m + b = S Namely: MemTable data memory size + chunk
+ * metadata memory size + static memory size = memory size for write

Review comment:
       format back




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org