`<jemalloc>: Unsupported system page size` warnings on 64K page size host

[Targunitoth]

Description

Running brufdev/many-notes:latest on a host with 64K page size (getconf PAGE_SIZE → 65536) produces repeated jemalloc warnings in the logs:

...
notes-php-1  | [10-Jan-2026 16:28:27] NOTICE: fpm is running, pid 126
notes-php-1  | [10-Jan-2026 16:28:27] NOTICE: ready to handle connections
notes-php-1  | ✅ NGINX + PHP-FPM is running correctly.
notes-php-1  | <jemalloc>: Unsupported system page size
notes-php-1  | <jemalloc>: Unsupported system page size
notes-php-1  | <jemalloc>: Unsupported system page size

Note: The container continues running despite warnings, but spams the logs.

[brufdev]

I had to research about this and found that the search engine I'm using (Typesense) uses jemalloc. They had a 64k page size in 0.27 but they had to revert back. The defaullt version is 4K, and they also offer a separate build with 16K.

Which device and OS are you using?

[Targunitoth]

Hey, thank you for looking into it!
Is it a problem that can easily be fixed in Many-Notes?
Would it be possible for you to add a parameter to set Typesense manually to version 0.27 or the correct large page size build?
I only saw 16k builds, not a 64k build, at https://typesense.org/docs/guide/install-typesense.html#large-page-size-build.

I'm using an ARM64 (aarch64) Oracle Linux Server:

> cat /etc/os-release
NAME="Oracle Linux Server"
VERSION="8.10"
ID="ol"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="8.10"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Oracle Linux Server 8.10"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:oracle:linux:8:10:server"
HOME_URL="https://linux.oracle.com/"
BUG_REPORT_URL="https://github.com/oracle/oracle-linux"

ORACLE_BUGZILLA_PRODUCT="Oracle Linux 8"
ORACLE_BUGZILLA_PRODUCT_VERSION=8.10
ORACLE_SUPPORT_PRODUCT="Oracle Linux"
ORACLE_SUPPORT_PRODUCT_VERSION=8.10

> uname -a
Linux main-server 5.4.17-2136.339.5.el8uek.aarch64 #3 SMP Mon Dec 23 20:53:59 PST 2024 aarch64 aarch64 aarch64 GNU/Linux

I'm also using the Docker Compose file from the 'docker-with-volumes' section of the README.md file.

[brufdev]

I don't think it's a good idea to use outdated versions, as you'll be missing out on fixes and improvements. They even said they had to revert from 64K.

That being said, it's possible to use a different version of Typesense. If you’re interested, and as a temporary solution for testing, create a Dockerfile file next to the compose.yaml with:

FROM brufdev/many-notes:latest
USER root
COPY --from=typesense/typesense:27.0 --chmod=755 /opt/typesense-server /opt/typesense-server
USER www-data

Then, adjust your compose.yaml file:

services:
  php:
    # image: brufdev/many-notes:latest
    build: .
...

Basically, you are still using my image, but you are replacing Typesense during the build phase. I haven't tested myself, as I don't have a 64K page size system. If it works, the ideal solution would be for Typesense to provide a 64K version in the last releases.