29 Oct 22:59
Re: memory consumption problem as collections get bigger
2008/10/29 Doruk Fisek <dfisek-8ahlAQKSdoL+ojMbLx6GBw@public.gmane.org>
I don't know how tellico does it, but I work for an app, and eg an xml file is 6.9 Mb, however, in reality this is a compressed file (like eg odf or docx format, also xml), uncompressed it is 48.7 Mb. In database format (xml is for export and import), this takes up two times 178 Mb on your hard disk (one for failsafe is a backup of last successfull data). However, because it is a database, one does not need to keep it in memory.
This example just to show things are not so easy to calculate and determine from the size of an xml file.
Benny
Wed, 29 Oct 2008 07:03:54 -0700, Robby Stephenson
<robby-9lFPeden07UgsBAKwltoeQ@public.gmane.org> :Even if you store all of the collection in RAM, 250 MB consumption for
> 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.
a 16 MB xml file (not zipped) seems too much. It's nearly 15 times the
original size.
I don't know how tellico does it, but I work for an app, and eg an xml file is 6.9 Mb, however, in reality this is a compressed file (like eg odf or docx format, also xml), uncompressed it is 48.7 Mb. In database format (xml is for export and import), this takes up two times 178 Mb on your hard disk (one for failsafe is a backup of last successfull data). However, because it is a database, one does not need to keep it in memory.
This example just to show things are not so easy to calculate and determine from the size of an xml file.
Benny
_______________________________________________ tellico-users mailing list tellico-users@... http://forge.novell.com/mailman/listinfo/tellico-users
RSS Feed