Re: [Sks-devel] Analyzing key server data

[dirk astrath]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

> Hockeypuck uses MongoDB or PostgreSQL as key storage backends. I
> don't know about MongoDB, but I know that while the tables are kept
> quite minimal in PostgreSQL, you could easily create a new table
> which inherits from the original one, adding more columns you can
> filter for. The size of the whole database in PostgreSQL is 21 GB.

I run two Hockeypuck-Instances (started with the same set of keys) on
two different machines (one machine at home, one notebook):

hockeypuck.fidocon.de (using nginx ... ;-) )

semi    (sksclient2) runs on a postgres-database
vdr-sg  (skslcient3) runs on a mongodb-database

There is one issue I detected using hockeypuck:

The "total number" is updated, but the daily/hourly statistics doesn't
seem to be stored after doing a restart of the hockeypuck service.

Both hockeypuck-servers are not 24/7 currently (due to limited memory
resources on both machines) ... ;-(

About the database-sizes:

berkley (sks)           Around 13 GB
mongodb (hockeypuck)    Around 20 GB
postgres (hockeypuck)   Around 25 GB

If somebody needs dumps of these databases feel free to contact me ... ;-)

Kind regards ...

PS: If you try to access the servers using IPv4 you'll reach one of my
sks-keyservers ... ;-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlW/cGgACgkQVuf/iihAxwjIjgCfYFg0HxUNbqNCvyA1ZGbRf/yH
DgEAn10bBU1Gs8pFSIviveQcJr8vg5+7
=Sfpv
-----END PGP SIGNATURE-----