3 ms·

I’m surprised at Elixir failing with 1M tasks. I’ve definitely done this sort of test with Erlang without an issue. Although I can’t really remember right now i

• crazydoggers 3y ago
  Almost certainly a system cofiguration issue. I’m pretty sure the default process limit on BEAM is something like 200K. Additionally I don’t see mention of updating file handles or anything else on the operating system. Maybe I’m cynical but this is what happens if you rely on chatGPT to give you programming answers without understanding the fundamentals first.
• sneako 3y ago
  “The maximum number of simultaneously alive Erlang processes is by default 262,144. This limit can be configured at startup. For more information, see the +P command-line flag in the erl(1) manual page in ERTS.” https://www.erlang.org/doc/efficiency_guide/advanced.html#:~:text=The%20maximum%20number%20of%20simultaneously%20alive%20Erlang%20processes%20is%20by%20default%20262%2C144 https://www.erlang.org/doc/efficiency_guide/advanced.html#:~....
• fwlr 3y ago
  Unless I’m missing something in the writeup, it doesn’t mention how much RAM is on the system. A little odd to mention the CPU and the OS but not the RAM, for a benchmark that doesn’t care about execution speed but does care about memory usage. It makes figuring out that Elixir error of “system limit reached” a little harder to figure out. edit: oh apparently it’s got nothing to do with memory, 1M just happens to be higher than the default process limit for Erlang and thus Elixir.
• conradfr 3y ago
  Also someone needs to tell ChatGPT that its Elixir code has a bug ;)