[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Memory Leak in NSString.m
From: |
Richard Frith-Macdonald |
Subject: |
Re: Memory Leak in NSString.m |
Date: |
Thu, 22 Feb 2001 10:27:39 +0000 |
On Thursday, February 22, 2001, at 10:05 AM, Helge Hess wrote:
> Frederic De Jaeger wrote:
> > Ok, I thought about a performance reason but I didn't think the
> > gain could be so important. Usually, you don't need to parse a big
> > property list in the inner loops of your code. It may only appends in the
> > startup of a prog. Does it really slow down the launch of an
> > application ?
>
> Eg in SKYRiX we parse a database model stored in a plist at startup.
> This plist is about 200K and startup (and more important: memory
> consumption) is significantly reduced by using a fast plist parser
> without -autorelease.
> (indeed I have modified the libFoundation parser in the same way).
>
> Large plists are not unusual for EOF like applications. Eg they are also
> useful for importing/exporting tables.
Yep ... and I use property-lists a lot, and even have them as a backup format
to restore from in case of database corruption ... in which case I'm parsing
hundreds of megabytes of property-lists (most individual lists a few K or tens
of K).