Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News Mono Roundup: iOS, Mobile Profile, and Concurrent GC

Mono Roundup: iOS, Mobile Profile, and Concurrent GC

This item in japanese


First up in the news is the release of Mono 3.0.3. Besides the normal bug fixes you would expect in a minor release, this introduces a new experimental garbage collector. Building on top of SGen, this garbage collector uses a process similar to Sun JVM’s concurrent mark-and-sweep (CMS) collector. Mark Probst continues,

A major garbage collection starts with an initial marking pause, during which all roots are scanned. Then it restarts the world and in the background a worker thread performs the marking and scanning of major heap objects, in the usual manner. When the concurrent marking phase is done, the collector stops the world again to finish up the collection in the final marking pause.

Another feature in Mono 3.0.3 better support for DTrace. The Mono garbage collectors “now feature multiple dtrace probes for users on MacOS and Solaris.”

Miguel de Icaza has revealed plans to alter the Mono Mobile profile. When it was originally created, the profile included the subset of APIs exposed to Silverlight developers. Now the Mono team wants to broaden the API by quite a bit. In the future it will be “based on the .NET 4.5 API, and removing the same bits we removed in the past: System.Configuration and the Registry.”

Finally, there has been a minor update to MonoTouch to support iOS 6.1.

Rate this Article


Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Why not study existing high performance VM's?

    by peter lin,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    So after so many years of work, Mono still doesn't have a high quality generational GC implementation. There's a big difference between reading papers on GC and taking time to study how existing VM's do it. The gap between theory and practice is wider than the pacific ocean.

    I really hope Mono developers take time to study existing implementations in detail and learn from the past. I know the Mono philosophy is "don't look at other systems" to avoid accidentally copying code, but that's a stupid policy. If a developer takes time (2-3 years) to study existing implementations and learn what to avoid, Mono could get a huge jump in performance. Needlessly re-inventing a square wheel makes Mono look like a follower, not an innovator.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p