Page History

...

1. For a scenario that generates 5 data points per second. (high one chunk one day) (5Hz frequency)

One day will generate 432,000 points (about 54 pages). Therefore, 1 chunk has 54 pages (about 3.4M). In scenarios like this, chunk and page is both necessary.

2. For a scenario that generates one data point per second. (second one chunk one day) (1Hz frequency)

One day will generate 86,400 points (about 11 pages). Therefore, 1 chunk has 11 pages (about 693K). In this scenario, chunk and page is both necessary. 

3. For a scenario that generates 5 data points per minute. (one chunk one day) (low 1/12Hz frequency)

One day will generate 7200 points (about 1 pages). Therefore, 1 chunk has 1 page (about 56.6K). In this scenario, chunk and page should only reserve one.

4. For a scenario that generates one data points point per minute. (one chunk one week) (minute 1/60Hz frequency)

One week will generate 10080 points (about 1.3 pages). Therefore, 1 chunk has 1~2 pages (about 79.3K). In this scenario, chunk and page should only reserve one.

Reserve both chunk and page: (3 levels of index in the whole TsFile)

• Chunk is the unit for I/O and page is the unit for query, which could supply multiple levels of I/Oindex

• Suitable for all kinds of query scenarios, whether aggregation query or raw data query

Reserve only page: (2 levels of index in the wholeTsFile)

• Suitable for APM scenariolow frequency scenario, in which 1 chunk has only 1~2 pages
  (Note: There has already been adapted structure for chunk statistics and page statistics from 0.12)

• Simple structure, which could reduce one level of I/Oindex

(III) Experiment about how to store PageHeader

...