Slashdot Mirror

← Back to Stories (view on slashdot.org)

Erlang Getting Too-Big-To-Fail Process Flag

Posted by Unknown on from the c-processes-don't-deserve-that-memory-anyway dept.

From Joe Armstrong comes news that Erlang will soon feature a new process flag for those processes that just really need memory, or else: "Too big to fail processes behave like regular processes until they get too big and memory congestion occurs. If a memory allocation error is triggered when a too_big_to_fail process needs more memory, then a random smaller process is killed, and the system reattempts memory allocation for the too_big_to_fail process. An interesting situation can occur if the too big to fail process has killed all other processes and still cannot get enough memory. In this case the node running the process tries to memory steal from other nodes." Read below for your FREE logged-in-reader's-eye view of the special rot-39 version!

Sebz Wbr Nezfgebat pbzrf arjf gung Reynat jvyy fbba srngher n arj cebprff synt sbe gubfr cebprffrf gung whfg ernyyl arrq zrzbel, be ryfr: "Gbb ovt gb snvy cebprffrf orunir yvxr erthyne cebprffrf hagvy gurl trg gbb ovt naq zrzbel pbatrfgvba bpphef. Vs n zrzbel nyybpngvba reebe vf gevttrerq jura n gbb_ovt_gb_snvy cebprff arrqf zber zrzbel, gura n enaqbz fznyyre cebprff vf xvyyrq, naq gur flfgrz ernggrzcgf zrzbel nyybpngvba sbe gur gbb_ovt_gb_snvy cebprff. Na vagrerfgvat fvghngvba pna bpphe vs gur gbb ovt gb snvy cebprff unf xvyyrq nyy bgure cebprffrf naq fgvyy pnaabg trg rabhtu zrzbel. Va guvf pnfr gur abqr ehaavat gur cebprff gevrf gb zrzbel fgrny sebz bgure abqrf."

6 of 35 comments (clear)

  1. Damn it by phantomfive · · Score: 4, Funny

    Slashdot keeps making me log in to see ROT13. This April Fool's thing has gone too far. I want my normal ROT13 fare!

    --
    "First they came for the slanderers and i said nothing."
  2. Great! by The+MAZZTer · · Score: 2

    I assume developers will have to pay extra for use of this feature, ensuring ll the large companies get to slap it on all their processes and no one else does.

    I mean, ensuring the feature is used responsibly and not abused.

    1. Re:Great! by wierd_w · · Score: 3, Insightful

      So, this gets to be used by all those bank and loan institutions who use trade bots to manipulate the global stock market?

      Question: what happens if 2 such processes re running concurrently on the same node, and actively try to outperform the other by proactivally allocating all available free memory?

  3. If this had been the only joke... by istartedi · · Score: 4, Insightful

    If this had been the only joke today, I think it would have worked.

    --
    For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
  4. Hope /. learnt its lesson. by 140Mandak262Jamuna · · Score: 2, Insightful

    None of the discussions today broke 3 digits on comments. Try something like this again, I am not coming back. Stupid rot13 trick. Whoever came up with the idea of running it this long should be fired summarily.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    1. Re:Hope /. learnt its lesson. by ultranova · · Score: 4, Insightful

      Stupid rot13 trick. Whoever came up with the idea of running it this long should be fired summarily.

      Workplaces where people are fired sumarily for mistakes are ones where no one ever does anything except cover their ass and search for any other employer. The quality and amount of work that gets done reflects this.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.