[gstreamer-bugs] [Bug 359653] GStreamer Binary Registry patch

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=359653

  GStreamer | gstreamer (core) | Ver: HEAD CVS




------- Comment #36 from Stefan Kost (gstreamer, gtkdoc dev)  2007-08-09 07:56 UTC -------
Another idea is to use a dictionary for the strings in the file and instead of
storing the string save a token-id taht references the string. Heres some data
that show the potential benefit:

-rw------- 1 ensonic users 521799  8. Aug 18:51 registry.i686.bin
-rw-r--r-- 1 ensonic users  38261  9. Aug 10:52 registry.i686.bin.bz2
-rw-r--r-- 1 ensonic users  50672  9. Aug 10:44 registry.i686.bin.gz
-rw-r--r-- 1 ensonic users 483166  9. Aug 10:44 registry.i686.txt
-rw-r--r-- 1 ensonic users 188759  9. Aug 10:45 registry.i686.txt.sort.uniq
-rw------- 1 ensonic users 983413 16. Jul 20:38 registry.i686.xml

one sees that the binary registry is nearly half of the xml one. But applying
gzip to it cuts it down to 9,7% (bzip2 to 7%)! Piping it through strings shows
that most of the stuff is text and applying sort | uniq shows that one could
easily save more that a half by using a dictionary.
That combined with the keeping the whole registry image in memory and using
static references in the features will save also runtime memory.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=359653.