gnunet-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNUnet-developers] caching proxy type data storage


From: Christian Grothoff
Subject: Re: [GNUnet-developers] caching proxy type data storage
Date: Sat, 22 Jun 2002 15:50:56 -0500
User-agent: KMail/1.4.1

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

On Saturday 22 June 2002 07:31 am, Igor Wronsky wrote:
> > GNUnet faces similar problems in storing data as a caching proxy
> > Last time i looked squid gave a choive of 3 different file systems to
> > store the data it retrieved, maybe GNUnet could get some ideas from them,
> > im sure they have reasons for not using a traditional database.
>
> Using 'traditional' database with gnunetd might be better choice
> in this case because data is always constant size <key,pair>
> elements. Or so I've understood. I don't think web cache
> data has such property naturally.

Well, it is 99% where the value is 1k, but it can also be a multiple of 1k. 
The key is always a 20 byte hashcode, which is to my dismay stored in
ASCII in the gdbm database (blowing it up to 41 bytes); I once tried to
store it as binary, but then gdbm stopped working. But yes, in general, we 
have very uniform content.

> Hehe, btw, with my previous experience I could do mysql support
> for gnunetd quite effortlessly. Probably it'd be inefficient as
> hell but ah all those nice statistics things that you can pull
> of with sql. ;) And there'd be off-the-shelf db repair and
> integrity checking. Though I did see that Christian
> already jumped to pull off some such utility for gnunet gdbm. ;D ;D

Nope, this utility is (going) to check the other database (lookup) and see if 
the lookup database is consistent with the content database.

Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9FOMw9tNtMeXQLkIRArb8AJ9gxgd05a6CVqj2Hcl+nn1mZsq5fgCfVErI
HD8PM9IN27PllIu5dgXWVEc=
=fUDl
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]