pertsevds
:erlang.memory(:total) shows 54877864,
VIRT shows 4G.
When I do ulimit -Sv 1048576 app just fails to start with error:
erts_mmap: Failed to create super carrier of size 1024 MB.
+MMscs 64
+MMsco true
+MMscrpm true
+Musac false
in vm.args does not reduce VIRT memory amount.
Searched this forum - found nothing of use.
Are there are any methods to reduce it?
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security











Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
dimitarvp
Does that reply by one of Erlang’s maintainers help?
pertsevds
App is not in a container.
In vm.args:
Both does not help.
Still the same 4G.
OS: Debian 10.
Elixir 1.15.
Erlang 26.0.2.
dimitarvp
Did you read the BEAM VM option he linked to? This is not about containers, it’s an option that should work regardless of where the app is started.
pertsevds
ERL_MAX_PORTS does not help.
I just tired +MIscs
+MIscs 128and mem usage dropped to 3188MB.dimitarvp
Hm, seems there is more that can be done but I am not aware of it, sorry.
Wonder if @garazdawi would be willing to help further.
garazdawi
I would use recon_alloc — recon v2.5.3 to get a view of what is using memory. Especially
recon_alloc:fragmentation/1can be helpful to look at.If you can provide a recon_alloc snapshot I can see if I can figure out what is using all the extra virtual memory.
pertsevds
Here is my recon_alloc snapshot: https://drive.google.com/file/d/1E5dCvdoug2DtPIl3P0dCM2DNU6lzx30o/view
garazdawi
The statistics for the Erlang allocators do not indicate that you are using a lot of virtual memory. What does
:erlang.system_info({:allocator,:erts_mmap})return?pertsevds
pertsevds
Summary from /proc/16025/smaps where 16025 - beam pid.
Some very strange region
And many empty regions with the size 65504 kB
My script for summary: