Re: metadata layout problems and some history

On Fri, Aug 06, 2010 at 04:34:40PM -0400, seth vidal wrote:
> Then what happened was all of the folks using/maintaining the tools
> found issues they had to work around and so we did:
> 
> - Yum eventually started generating sqlite dbs of the same data that was
> in the xml files to speed up access to the data. 
> 
> - Zypper uses .solv files to do much the same thing for the satsolver
> code. 

Yes, but we use them internally and don't download them from the
server. It works for us because xml -> solv conversion doesn't take
much time:

$ ls -l fedora12upprimary.xml.gz
-rw-r--r-- 1 mls suse 2843370 Aug  7 17:25 fedora12upprimary.xml.gz
$ gunzip < fedora12upprimary.xml.gz | (time repomdxml2solv > /dev/null)
0.896u 0.062s 0:00.96 98.9%     0+0k 0+0io 0pf+0w

So it takes about a second to convert the 2.8 Mbytes xml file to
solv. I guess creating the sqlite database is a bit slower, so you
chose to do it on the server and not on the client.

As parsing the data file is not the bottleneck for us, anything that
reduces the transfer size is a good thing. A switch to sqlite
would hurt us, as the sqlite database is currently bigger than the
compressed xml. (This is probably worse if lzma is used
instead of gzip.)

(I have no e-mail access for the next two weeks. Klaus and Duncan,
could you please answer any questions?)

Cheers,
  Michael.

-- 
Michael Schroeder                                   [email protected]
SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}