On Thu, Oct 31, 2013 at 12:12 PM, Robert O'Callahan <[email protected]>wrote:
> Since tasks don't share heaps, bounding their memory usage seems > tractable; it becomes an accounting problem. Instead of using explicit > counters I suggest following the lead of Gecko's MemShrink project and > building infrastructure to compute the memory usage of a task by walking > its heap. > The idea then would be that if the program as a whole gets into a low-memory situation, you compute the heap size of each task and kill some of them. It's a bit like OOM killing in operating systems, but in Rust you have a lot more information available (and we can ask developers to provide even more if it's helpful), so we should be able to make more sensible decisions. Rob -- Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt wyeonut thoo mken.o w * *
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
