Re: Mono/GTK#/Tomboy

[Federico Mena Quintero <federico ximian com>]

On Fri, 2006-07-14 at 10:50 +0200, Murray Cumming wrote:

> I don't believe that you've adressed the memory problems, though these are
> not specific to Mono. We maybe can handle one highlevel runtime, but 2
> highlevel runtimes seems to be getting silly.

baseline.py:
	import gtk

	window = gtk.Window ()
	window.show ()
	gtk.main ()
pmap says:
3532K writable-private, 14284K readonly-private, and 28K shared

baseline.cs:
	using Gtk;

	class Foo {
		public static void Main (string[] args)
		{
			Gtk.Window window;

			Gtk.Application.Init ();
			window = new Gtk.Window (Gtk.WindowType.Toplevel);
			window.Show ();
			Gtk.Application.Run ();
		}
	}
pmap says: 
3324K writable-private, 16224K readonly-private, and 4868K shared

"Look, Mono uses 200 KB less writable memory!  And, uh, it shares more
data!  Or something!"

These numbers mean nothing.  Those tiny "apps" are perfectly useless.

> Also, Tomboy is an applet, intended to replace the commonly-used sticky
> notes applet, so it's likely to take up memory all the time. (I haven't
> had a response to my notes->tomboy transistion questions [1] but that's a
> non-mono issue.)

The main point about performance is whether users think it is a good
deal.

So Firefox eats 400 MB.  Do I think it's a good deal?  Absolutely!  It's
the best browser out there.

So Tomboy eats 15 MB.  Do I think it's a good deal?  Absolutely!  It's
the best note-taking app I know.

So OpenOffice takes 100 MB.  Do I think it's a good deal?  Absolutely!
I wouldn't go back to Magicpoint EVER.

So F-spot takes <whatever> MB.  So what?  It's the best photo
cataloguing app we have.

Can those numbers be improved?  Absolutely.  And we should do it.

  Federico