Skip to content

Conversation

yznima
Copy link
Contributor

@yznima yznima commented Feb 3, 2025

This is an additional step to fix the same issue as #14688. We've noticed this occurs when the # of CPUs is set to 1.

@yznima yznima force-pushed the fix-jemalloc-narenas branch from 3a06673 to 9ad5e4f Compare February 3, 2025 22:15
@yznima yznima changed the title set cpu_count to 1 if no other way set jemalloc narenas to 1 if no other way to get it Feb 3, 2025
@duckdb-draftbot duckdb-draftbot marked this pull request as draft February 3, 2025 22:15
@yznima
Copy link
Contributor Author

yznima commented Feb 3, 2025

@Mytherin Could you review please?

(cherry picked from commit 86b2084e1f82c000993c01db1d56987a1c6d719d)
@yznima yznima force-pushed the fix-jemalloc-narenas branch from 9ad5e4f to b29d2ac Compare February 3, 2025 22:20
@Mytherin Mytherin changed the base branch from main to v1.2-histrionicus February 3, 2025 22:30
@Mytherin Mytherin marked this pull request as ready for review February 3, 2025 22:30
@Mytherin Mytherin merged commit 77c32fe into duckdb:v1.2-histrionicus Feb 4, 2025
50 checks passed
@Mytherin
Copy link
Collaborator

Mytherin commented Feb 4, 2025

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants