Skip to content

Read Parquet files even faster, take 2#49539

Merged
al13n321 merged 1 commit intomasterfrom
readat
Jun 2, 2023
Merged

Read Parquet files even faster, take 2#49539
al13n321 merged 1 commit intomasterfrom
readat

Conversation

@al13n321
Copy link
Copy Markdown
Member

@al13n321 al13n321 commented May 5, 2023

Changelog category (leave one):

  • Performance Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

  • Better performance when reading local Parquet files (through parallel reading).

Parquet's parallel random reads from local file are now actually parallel (pread() calls or memcpy from mmap), instead of locking two mutexes for no reason.

In #47964 I refactored things to use SeekableReadBufferFactory in more places, as the abstraction for random-access "files" (local/http/s3). I think that was a mistake. This PR re-refactors everything in the opposite direction: it adds a thread-safe positioned-read method in SeekableReadBuffer and uses it whenever parallel random reading is needed (ParallelReadBuffer and ParquetBlockInputFormat). This turned out better than the factory stuff, I think: less (?) code, fewer boilerplate objects, less useless extra cpu work (like maintaining a pool of ReadBuffers to reuse), less awkward code like ifs everywhere for buffer vs factory. The factory is removed altogether.

Also fixed a confusing error message when getting HTTP 404 error: it used to say "Not a Parquet file" because asArrowFileLoadIntoMemory() was catching exceptions too eagerly.

@al13n321 al13n321 marked this pull request as draft May 5, 2023 04:44
@al13n321 al13n321 marked this pull request as ready for review May 5, 2023 04:59
@al13n321 al13n321 marked this pull request as draft May 5, 2023 05:00
@al13n321 al13n321 marked this pull request as ready for review May 5, 2023 23:06
@al13n321
Copy link
Copy Markdown
Member Author

al13n321 commented May 5, 2023

(This PR depends on #49533 , so CI doesn't run on it yet. But it's ready for review, and CI ran on an older version of this PR: #49121 )

Base automatically changed from httcpp to master May 7, 2023 04:11
@robot-clickhouse-ci-2 robot-clickhouse-ci-2 added the pr-performance Pull request with some performance improvements label May 7, 2023
@robot-clickhouse-ci-2
Copy link
Copy Markdown
Contributor

robot-clickhouse-ci-2 commented May 7, 2023

This is an automated comment for commit bbfbf97 with description of existing statuses. It's updated for the latest CI running
The full report is available here
The overall status of the commit is 🔴 failure

Check nameDescriptionStatus
AST fuzzerRuns randomly generated queries to catch program errors. The build type is optionally given in parenthesis. If it fails, ask a maintainer for help🟢 success
CI runningA meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR🟢 success
ClickHouse build checkBuilds ClickHouse in various configurations for use in further steps. You have to fix the builds that fail. Build logs often has enough information to fix the error, but you might have to reproduce the failure locally. The cmake options can be found in the build log, grepping for cmake. Use these options and follow the general build process🟢 success
Compatibility checkChecks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help🟢 success
Docker image for serversThe check to build and optionally push the mentioned image to docker hub🟢 success
Fast testNormally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here🟢 success
Flaky testsChecks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integrational tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc🟢 success
Install packagesChecks that the built packages are installable in a clear environment🟢 success
Integration testsThe integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests🟢 success
Mergeable CheckChecks if all other necessary checks are successful🟢 success
Performance ComparisonMeasure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests🟢 success
Push to DockerhubThe check for building and pushing the CI related docker images to docker hub🟢 success
SQLancerFuzzing tests that detect logical bugs with SQLancer tool🟢 success
SqllogicRun clickhouse on the sqllogic test set against sqlite and checks that all statements are passed🟢 success
Stateful testsRuns stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc🟢 success
Stateless testsRuns stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc🔴 failure
Stress testRuns stateless functional tests concurrently from several clients to detect concurrency-related errors🔴 failure
Style CheckRuns a set of checks to keep the code style clean. If some of tests failed, see the related log from the report🟢 success
Unit testsRuns the unit tests for different release types🟢 success
Upgrade checkRuns stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts🟢 success

@al13n321 al13n321 force-pushed the readat branch 2 times, most recently from 350ae48 to bb92b55 Compare May 8, 2023 22:11
@robot-clickhouse-ci-1 robot-clickhouse-ci-1 added the submodule changed At least one submodule changed in this PR. label May 8, 2023
@Avogar Avogar self-assigned this May 10, 2023
@robot-clickhouse robot-clickhouse removed the submodule changed At least one submodule changed in this PR. label May 11, 2023
@zhanglistar
Copy link
Copy Markdown
Contributor

@al13n321 When do you will rewrite parquet reader?

@al13n321
Copy link
Copy Markdown
Member Author

@al13n321 When do you will rewrite parquet reader?

Not sure, maybe soon. #49367 was kind of an experiment to see if it's as easy as it seems, and the answer turned out to be "no", predictably :)

@liuneng1994
Copy link
Copy Markdown
Contributor

I'm reimplementing a parquet reader based on the ClickHouse code. Perhaps an experimental PR can be submitted in June.

@al13n321
Copy link
Copy Markdown
Member Author

I'm reimplementing a parquet reader based on the ClickHouse code. Perhaps an experimental PR can be submitted in June.

Nice! Then I'm not going to do it, for now.

Comment on lines +638 to +640
if (!cancelled)
{
}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is it?)

Copy link
Copy Markdown
Member

@Avogar Avogar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks much better and simplier than it was, great work!

Need to check why integration tests failed

@al13n321 al13n321 merged commit b51064a into master Jun 2, 2023
@al13n321 al13n321 deleted the readat branch June 2, 2023 01:48
baibaichen added a commit to Kyligence/gluten that referenced this pull request Jun 3, 2023
zzcclp pushed a commit to apache/gluten that referenced this pull request Jun 3, 2023
* [GLUTEN-1632][CH]Daily Update Clickhouse Version (20230603)

* Fix Build since ClickHouse/ClickHouse#50400

* Fix Build since ClickHouse/ClickHouse#49539

* Workaround protoc's issue(protocolbuffers/protobuf#9378).

---------

Co-authored-by: kyligence-git <[email protected]>
Co-authored-by: Chang Chen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-performance Pull request with some performance improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants