Miguel de Icaza wrote: > Hello, > Hi,
> >> Jits on the desktop are usually bad not just because they do take more >> memory but also because you need the build system of mono installed >> which means more bloat. > > Considering that Gtk# applications consume less memory than PyGtk > applications am puzzled by this blank statement. > > Am not quite sure what you mean by "the build system of Mono", there is > no such thing as "the build system of mono". Maybe you mean that you > need to have the "mono" command installed? That + all the assemblies. Contrast with GCJ which links in only whats needed to create a compact native stand alone executable - that is what AOT should be IMO. (is the SoC project to create a linker basically this?) > >> Every compacting GC automatically doubles memory use - you have two >> managed heaps ergo twice the RAM required. If you copy MS and go for a >> three generation one then you risk trebling memory use over using a >> non-compacting one. > > The extra memory used for a compacting collector is in the nurseries. A > compacting GC can allocate memory during the compacting phase for > temporary objects, and release it back to the OS when its done. > > So certainly during a collection you would notice more memory usage, but > it would go back to the used memory after the collection is over. so in other words it will spike every now and again EG if under Boehm GC I have 50MB heap then in compacting mode its going to spike from 50 to 100+ MB (how much higher depends on the no. of generations you have and how incremental it is of course) Im not sure how this helps mono though except maybe you can claim it will be faster. -- Mr Jamie McCracken http://jamiemcc.livejournal.com/ _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
