29 Oct 15:25
Re: memory consumption problem as collections get bigger
2008/10/29 Robby Stephenson <robby-9lFPeden07UgsBAKwltoeQ@public.gmane.org>
If things are in an sqlite embedded database as eg Amarok collection, you can avoid this. Undo is possible by going back in the database logs. Anyway, with all the database based apps now, people get used to atomic saves in apps that handle collections
Benny
On Wednesday 29 October 2008, Doruk Fisek wrote:
> Hi,
>
> I'm using Tellico for a music collection, my .tc file is about 2 MB.
> When I unzip it, it's about 16 MB as xml data.
>
> When I open the file, Tellico consumes about 250 MB of my computer's
> memory. I notice that as the collection grows, so does the memory
> Tellico takes up.
>
> I can't open this collection on my 512 MB machine with other
> applications running since it causes huge swap activity.
>
> Is this normal behavior? If so, is there anyway to improve Tellico to
> consume less memory?
It's been a chronic problem for some folks, and I've tried a few things with
reducing the memory usage, but like you point out, it seems to grow too
much with respect to the file size.
Tellico holds all the collection data in RAM once the file is opened. That's
obviously not going to work well with really big collections, it's just the
way I wrote it. If you delete your data file once it's loaded, Tellico can
save it again completely.
If things are in an sqlite embedded database as eg Amarok collection, you can avoid this. Undo is possible by going back in the database logs. Anyway, with all the database based apps now, people get used to atomic saves in apps that handle collections
Benny
_______________________________________________ tellico-users mailing list tellico-users@... http://forge.novell.com/mailman/listinfo/tellico-users
RSS Feed