I've not done any actual work, however in the past, it's been very little. It can't be zero, 'cos monotouch is "extra", but it's as close to zero as you can get.
Geoff commented in the past that load time depends more on what you do during load, than the framework - an MT app can spin up quicker than a Obj-C one if it's done right. One of the main things for load time was to get as much stuff out of your ApplicationFinishedLaunching as you can - move it to background threads etc. So far, it's not been a problem, or even noticable. On Wed, Aug 3, 2011 at 13:58, kbudris <[email protected]> wrote: > Has anyone done benchmarking of an app implemented in MonoTouch vs. > Objective-C to determine what, if any, performance cost we pay for the > convenience of MonoTouch? Do we take any hit on launching and/or running a > MonoTouch app? > > -- > View this message in context: > http://monotouch.2284126.n4.nabble.com/Performance-cost-of-MonoTouch-vs-Objective-C-tp3715348p3715348.html > Sent from the MonoTouch mailing list archive at Nabble.com. > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch > -- Nic Wise t. +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise b. http://www.fastchicken.co.nz/ mobileAgent (for FreeAgent): get your accounts in your pocket. http://goo.gl/IuBU Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2 _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
