Hi Chris. .net and mono always have some overhead, so I think it's normal.
Instead of creating a dozen of processes, why don't you create just one and as many buses as you need inside that process? Cheers. El 31/08/2014 02:52, "Chris Morgan" <[email protected]> escribió: > Hello. > > I'm looking to use mono for some dbus bridges with dbus-sharp. I've got a > pretty simple bridge, a couple of classes and a single dbus interface that > bridges to a socket in a console application. It looks like each instance > has ~14MB of memory overhead, from smem output: > > 30038 cmorgan mono display_interface.exe 0 16792 19650 > 23488 > > So, 16.7MB USS, 19.65MB PSS and 23.48MB RSS. > > Using mono 3.4 on Fedora 20. > > > I ran the alloc profiler on the application and it looks like there was > some 700k of memory allocated in the application itself, quite small > compared to the process memory. > > I'd like to be able to use mono to create a dozen or more of these dbus > bridges but the embedded arm system I'm using only has 512MB of ram. > > I haven't tested on the arm platform yet, but I'm assuming a similar > amount of overhead for each process. > > Is this a normal amount of overhead per-process? Thoughts on how I might > be able to reduce it? > > Chris > > > _______________________________________________ > Mono-list maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/mono-list > >
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
