HTHou commented on a change in pull request #2601:
URL: https://github.com/apache/iotdb/pull/2601#discussion_r579569066



##########
File path: docs/UserGuide/Comparison/TSDB-Comparison.md
##########
@@ -284,101 +284,91 @@ It is somehow right. But, if you consider the 
performance, you may change your m
 
 #### quick review
 
-Given a workload:
-
 * Write:
 
-10 clients write data concurrently. The number of storage group is 50. There 
are 1000 devices and each device has 100 measurements (i.e.,, 100K time series 
totally).
-The data type is float and IoTDB uses RLE encoding and Snappy compression. 
-IoTDB uses batch insertion API and the batch size is 100 (write 100 data 
points per write API call).
+We test the performance of writing from two aspects: *batch size* and *client 
num*. The number of storage group is 10. There are 1000 devices and each device 
has 100 measurements(i.e.,, 100K time series total).
 
 * Read:
 
-50 clients read data concurrently. Each client just read data from 1 device 
with 10 measurements in one storage group.
+10 clients read data concurrently. The number of storage group is 10. There 
are 10 devices and each device has 10 measurements (i.e.,, 100 time series 
total).
+The data type is *double*, encoding type is *GORILLA*
 
-IoTDB is v0.9.0.
+The IoTDB version is v0.11.1.
 
 **Write performance**:
 
-We write 112GB data totally.
+* batch size:
+
+10 clients write data concurrently.
+IoTDB uses batch insertion API and the batch size is distributed from 1ms to 
1min (write N data points per write API call).
 
 The write throughput (points/second) is:
 
-![Write Throughput 
(points/second)](https://user-images.githubusercontent.com/1021782/80472896-f1db0e00-8977-11ea-9424-96bf0021588d.png)
-<span id = "exp1"> <center>Figure 1. Write throughput (points/second) IoTDB 
v0.9</center></span>
+![Batch Size with Write Throughput 
(points/second)](https://user-images.githubusercontent.com/24886743/106254214-6cacbe80-6253-11eb-8532-d6a1829f8f66.png)
+<span id = "exp1"> <center>Figure 1. Batch Size with Write throughput 
(points/second) IoTDB v0.11.1</center></span>
+
 
+The write delay (ms) is:
 
-The disk occupation is:
+![Batch Size with Write Delay 
(ms)](https://user-images.githubusercontent.com/24886743/106251391-df1b9f80-624f-11eb-9f1f-66823839acba.png)
+<center>Figure 2. Batch Size with Write Delay (ms) IoTDB v0.11.1</center>
 
-![Disk 
Occupation](https://user-images.githubusercontent.com/1021782/80472899-f3a4d180-8977-11ea-8233-268ad4e3713e.png)
-<center>Figure 2. Disk occupation(GB) IoTDB v0.9</center>
+* client num:
+
+client num is distributed from 1 to 50.

Review comment:
       ```suggestion
   The client num is distributed from 1 to 50.
   ```




----------------------------------------------------------------
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:
[email protected]


Reply via email to