Skip to content

Reduce memory usage of inserts to JSON by using adaptive write buffer size#69272

Merged
Avogar merged 6 commits intoClickHouse:masterfrom
Avogar:json-memory-usage
Sep 10, 2024
Merged

Reduce memory usage of inserts to JSON by using adaptive write buffer size#69272
Avogar merged 6 commits intoClickHouse:masterfrom
Avogar:json-memory-usage

Conversation

@Avogar
Copy link
Copy Markdown
Member

@Avogar Avogar commented Sep 4, 2024

Changelog category (leave one):

  • Improvement

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

Reduce memory usage of inserts to JSON by using adaptive write buffer size. A lot of files created by JSON column in wide part contains small amount of data and it doesn't make sense to allocate 1MB buffer for them.

Examples of the changes in memory usage:

Table:

create table test (json JSON) engine=MergeTree order by tuple() settings min_rows_for_wide_part=1, min_bytes_for_wide_part=1;

Before:

avogar-dev :) insert into test from infile 'ghdata_sample.json' format JSONAsObject

Elapsed: 2.064 sec. Processed 5.00 thousand rows, 14.74 MB (2.42 thousand rows/s., 7.14 MB/s.)
Peak memory usage: 6.99 GiB.

avogar-dev :) insert into test select * from s3('s3://clickhouse-public-datasets/gharchive/original/2024-07-01-{0..4}.json.gz', NOSIGN, JSONAsObject)

Elapsed: 33.941 sec. Processed 884.76 thousand rows, 491.26 MB (13.53 thousand rows/s., 7.51 MB/s.)
Peak memory usage: 23.13 GiB.

After:

avogar-dev :) insert into test from infile 'ghdata_sample.json' format JSONAsObject

Elapsed: 1.626 sec. Processed 5.00 thousand rows, 14.74 MB (3.08 thousand rows/s., 9.07 MB/s.)
Peak memory usage: 354.46 MiB.

avogar-dev :) insert into test select * from s3('s3://clickhouse-public-datasets/gharchive/original/2024-07-01-{0..4}.json.gz', NOSIGN, JSONAsObject)

Elapsed: 34.765 sec. Processed 884.76 thousand rows, 491.26 MB (13.52 thousand rows/s., 7.51 MB/s.)
Peak memory usage: 7.65 GiB.

Documentation entry for user-facing changes

  • Documentation is written (mandatory for new features)

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

CI Settings (Only check the boxes if you know what you are doing):

  • Allow: All Required Checks
  • Allow: Stateless tests
  • Allow: Stateful tests
  • Allow: Integration Tests
  • Allow: Performance tests
  • Allow: All Builds
  • Allow: batch 1, 2 for multi-batch jobs
  • Allow: batch 3, 4, 5, 6 for multi-batch jobs

  • Exclude: Style check
  • Exclude: Fast test
  • Exclude: All with ASAN
  • Exclude: All with TSAN, MSAN, UBSAN, Coverage
  • Exclude: All with aarch64, release, debug

  • Run only fuzzers related jobs (libFuzzer fuzzers, AST fuzzers, etc.)
  • Exclude: AST fuzzers

  • Do not test
  • Woolen Wolfdog
  • Upload binaries for special builds
  • Disable merge-commit
  • Disable CI cache

@Avogar Avogar assigned Avogar and CheSema and unassigned Avogar Sep 4, 2024
@robot-ch-test-poll1 robot-ch-test-poll1 added the pr-improvement Pull request with some product improvements label Sep 4, 2024
@robot-clickhouse-ci-2
Copy link
Copy Markdown
Contributor

robot-clickhouse-ci-2 commented Sep 4, 2024

This is an automated comment for commit 72dbc82 with description of existing statuses. It's updated for the latest CI running

✅ Click here to open a full report in a separate page

Successful checks
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
BuildsThere's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
ClickBenchRuns [ClickBench](https://github.com/ClickHouse/ClickBench/) with instant-attach table✅ success
Compatibility checkChecks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help✅ success
Docker keeper imageThe check to build and optionally push the mentioned image to docker hub✅ success
Docker server imageThe check to build and optionally push the mentioned image to docker hub✅ success
Docs checkBuilds and tests the documentation✅ 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. Integration 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
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
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✅ success
Stress testRuns stateless functional tests concurrently from several clients to detect concurrency-related errors✅ success
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

@Avogar Avogar added this pull request to the merge queue Sep 10, 2024
Merged via the queue into ClickHouse:master with commit d226b13 Sep 10, 2024
@Avogar Avogar deleted the json-memory-usage branch September 10, 2024 16:25
@robot-clickhouse-ci-1 robot-clickhouse-ci-1 added the pr-synced-to-cloud The PR is synced to the cloud repo label Sep 10, 2024
@Avogar Avogar mentioned this pull request Sep 17, 2024
56 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-improvement Pull request with some product improvements pr-synced-to-cloud The PR is synced to the cloud repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants