You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're working on a Kafka Streams Kotlin application and using the distroless Java image from gcr.io along with the @io_bazel_rules_docker//kotlin:image.bzl rule (_kt_jvm_image = "kt_jvm_image") to build our image.
We've encountered a need to change the default memory allocator to jemalloc, but we're having trouble figuring out the best way to integrate it into our application with Bazel.
Our current approach involves installing jemalloc and setting the LD_PRELOAD environment variable, but we're unsure how to seamlessly inject jemalloc into our Bazel build process.
Does anyone have experience or suggestions on how to accomplish this with Bazel? Any insights or guidance would be greatly appreciated!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We're working on a Kafka Streams Kotlin application and using the distroless Java image from gcr.io along with the @io_bazel_rules_docker//kotlin:image.bzl rule (_kt_jvm_image = "kt_jvm_image") to build our image.
We've encountered a need to change the default memory allocator to jemalloc, but we're having trouble figuring out the best way to integrate it into our application with Bazel.
Our current approach involves installing jemalloc and setting the LD_PRELOAD environment variable, but we're unsure how to seamlessly inject jemalloc into our Bazel build process.
Does anyone have experience or suggestions on how to accomplish this with Bazel? Any insights or guidance would be greatly appreciated!
Thanks in advance for your help!
Beta Was this translation helpful? Give feedback.
All reactions