[maemo-developers] [maemo-developers] Re: Python memory use (was: Maemo 2.0 final release available)
From: Ross Burton ross at burtonini.comDate: Mon Jul 10 18:21:59 EEST 2006
- Previous message: Python memory use (was: [maemo-developers] Maemo 2.0 final release available)
- Next message: [maemo-developers] Developing kiosk applications in Python (connectivity, buttons, backlight)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 2006-07-10 at 16:38 +0300, Tommi Komulainen wrote: > On Mon, 2006-07-10 at 09:15 -0300, ext Gustavo Sverzut Barbieri wrote: > > On 7/10/06, Tommi Komulainen <tommi.komulainen at nokia.com> wrote: > > > 2. memory consumption > > > 4. run-time speed? > > > > These are not an issue, really. Since python does garbage collect, in > > the long run it may show even more memory efficient than pure C, which > > may leak. > > Memory leaks in C are fixable, just takes some effort. OTOH the python > interpreter / wrapper overhead are not. I've also been told that python > never releases memory back to the system, though that ought to be > fixable. Whether those are significant issues I haven't measured, just > some rough edges to keep in mind. PyGTK also initialises every type in GTK+ at startup instead of on-demand (as with C applications), which is part of the slow startup/high memory usage problem. Ross -- Ross Burton mail: ross at burtonini.com jabber: ross at burtonini.com www: http://www.burtonini.com./ PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF
- Previous message: Python memory use (was: [maemo-developers] Maemo 2.0 final release available)
- Next message: [maemo-developers] Developing kiosk applications in Python (connectivity, buttons, backlight)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]