Throughput Performance Testing of TsFile
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- performance
Research direction
The issue reports TsFile write and read benchmarks on a specified Java commit, but names no source files, tests, entry points, or requested change. First clarify whether the goal is to reproduce, investigate, or improve the reported throughput, then identify the benchmark entry point and define target results as the completion criteria.
Written by the indexing model from the issue text.
Description
Configuration
12th Gen Intel(R) Core(TM) i9-12900KS
Disk Write Speed ：3.1GB/s
Disk Read Speed : 4.6GB/s
WSL2 , Ubuntu 22.04.
Language : Java
Commit : 02727c5a9c98ca754b5a35a2cdf5d2f698934853
Schema Configuration
Device Num : 50
Sensor Num On One Device : 50
DataType : INT32
CompressionType : LZ4
Encoding : TS_2DIFF
Write Speed Test
1,000,000 points every sensor.
50 * 50 * 1,000,000 points totally.
Writing data using a tablet which has 50 sensors and a maximum of 100,000 rows
Total Write Time : 73.059s
Total Points Num : 2500,000,000 points
Write Spped: 34,218,918 points/s.
Read Speed Test
Conduct data read tests using the TsFile generated from the write tests.
Get all data from only one timeseries:
query all cost: 0.17s
query get points: 1,000,000points
query speed : 5882352.94117647points/s
Get all data from only one device( 50 sensors):
query all cost: 1.405s
query get points: 50,000,000points
query speed :35,587,188 points/s
Get all data from all devices (50 devices * 50 sensors):
query all cost: 145.249s
query get points: 2,500,000,000points
query speed: 17,211,822.46points/s
- Dominant language
- Java
- Stars
- 206
- Forks
- 105
- Avg merge
- 22h 54m
- Merged PRs (30d)
- 27
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/tsfile
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
c++ enhancement feature help wanted performance
Difficulty 5/5 Over a week Newbie friendliness 35/100
apache/tsfile#943 · 1 comment ·
Maintainers usually reply within 1 day
-
C feature go help wanted
Difficulty 5/5 Over a week Newbie friendliness 30/100
apache/tsfile#924 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
[Feature] Support appending to a normally closed TsFile in C++ and C APIsMay be free again @Adarsh-Me claimed this 30 days ago, and no pull request is open. OpenC c++ feature help wanted
apache/tsfile#923 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
type: possible bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
grimmory-tools/grimmory#2850 · 1 comment ·
Maintainers usually reply within 1 day
-
pdf
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
portfolio-performance/portfolio#6103 ·
Maintainers usually reply within 7 days