4 ms·
I can see how you would think that, yes. In practice I haven't noticed it except in super rare cases where processes (actors) hold on to huge binaries / strings
by pdimitar 3y ago
I can see how you would think that, yes. In practice I haven't noticed it except in super rare cases where processes (actors) hold on to huge binaries / strings -- which is one of the weak points of BEAM's GC.
- fidotron 3y agoMy experience of this is not theoretical.
- pdimitar 3y agoMaybe you should write a blog post about it, many in the Elixir's ecosystem are very serious devs and are always looking at ways to improve it.
- fidotron 3y agoThere are entire github repos dealing with it. Frankly the Elixir ecosystem, which is not without merit, is more interested in perpetuating the myth of magic scalability by virtue of the beam.
- pdimitar 3y agoFrankly I am seeing that as a myth, you seem to have made up your mind some time ago or judged by 1-2 occasions. I am on ElixirForum every day and worked with Elixir for 7 years and have never seen anyone "perpetuate myths". I've seen some people willing to "increase adoption" which was always met with resistance by the wider community -- we believe growth should be organic. Pretty sad stance from you though, I have no idea why people get so ticked off when another programmer wants to tell them about a secret weapon. If you are not willing to try it, that's fair. Say that. Claiming you know stuff about the ecosystem while a guy who is there every day is not seeing that at all comes across as... strange. Biased. And not arguing in good faith. :(
- fidotron 3y ago> If you are not willing to try it, that's fair. Say that. Claiming you know stuff about the ecosystem while a guy who is there every day comes across as... strange. Biased. And not arguing in good faith. :( I am not willing to drag others, such as those that wrote the repos, into a technical discussion with people out to act as you are.
- pdimitar 3y agoI really don't get your replies and why their tone has to be the way it is but, have it your way. I tried.
- DoesntMatter22 3y agoThe guy you are responding to was completely calm and reasonable. Didn't say anything attacking or otherwise. I'm not sure why you are seemingly trying to cast him (and the Beam) in such a bad light, with seemingly no reason to back it up.
- fidotron 3y agoHe is adopting the missionary tactic of feigning a desire for discussion when it is just veiled evangelism.
- DoesntMatter22 3y agoHe seemed to be asking you to back up your claims and you seem to be just saying claiming that you don't need to and he is the problem...
- deleted 3y ago[deleted]
- fidotron 3y agoBoth of you are afflicted by that logical fallacy of failing to understand that you not encountering a phenomenon does not mean it does not happen or is rare, it just means you didn't encounter it. If you try telling people that did encounter that phenomenon that in practice they wouldn't/didn't then you shouldn't be surprised if they question why they started talking to you in the first place.
- throwawaymaths 3y agoThe big offenders is serializing huge jsons and chucking small binaries slices from that into an ets table. Also concatenating binaries. Don't do that, use an iolist
- pdimitar 3y agoYep. Has bitten me in the bottom before.
- fud101 3y agoI've been bit by this. In reality you need to know your shit when it comes to tuning the Beam and GC to achieve decent performance under load without triggering OOM.
- pdimitar 3y agoNot denying it, yeah, it's a blind spot and it's one of the more advanced topics when you start having actually loaded nodes in production.