sks-devel
[Top][All Lists]
Advanced

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

Re: [Sks-devel] 3 million keys & and community help requested


From: John Clizbe
Subject: Re: [Sks-devel] 3 million keys & and community help requested
Date: Sat, 15 Oct 2011 06:51:02 -0500
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.20pre) Gecko/20110606 Mnenhy/0.8.4 SeaMonkey/2.0.15pre

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

Gabor Kiss wrote:
>> We hit 3 million keys as far as i can see. Congrats to all and i hope
>> we will receive the next 3 millions a bit faster ;-)

key #3000000 was the first key on 2011-10-14 after 09:00 CDT (US/Central)
(At keyserver.gingerbear.net)

The present rate for new keys seems to be ~353.1724 keys/day. 1000000 new keya
at that rate would require 2831.478 days or 7.752 years.

- ------------------------------------------------------------------------------

The recent 1.0.2 release would not have happened without additional patches from
Kim Minh-Kaplan and Hawke Lapmpe as well as extensive XHTML 1.0 testing and
hints from John Marshall. THAT was the way a F/OSSS project such as ours should
work.

I think rather than looking at ways to accumulate more keys in less time, we
might do ourselves better with looking at ways to do what we do better,

Are we using the most efficient schema for the database? Page sizes and other
default DB creation settings and tunables? Are there DB Stores which could yield
better preformance on standard or lowend hardware -- it doesn't take much to run
a keyserver, e.g., 500MHz US-IIi Sun Blade 100/2GB/ 2x 2GB IDE.

I still think we have a ways to go to make SKS portable to more operating
systems -- I think MacPorts provides the better framework than Fink to do this
on OS X. I had initally started working on a Solaris port using BlastWave, but
this seem to have gone dormant there and OpenCSW looks like that path foward.
Both of these are somewhat outliers for the launchd/SMF frameworks to put SKS in
place as a service, both require an XML description as well as a sh/bash
start/atop/restart script. I've been working on a Slackbuild for Slackware.

Cygwin port anyone? Ocaml and bdb are already there :-)

Another request that has came up in the issues is for us to provide examples of
the front page index.{html,htm,xhtm} along with .es/.js support. I need testers
for the .es/.js & XHTML support. It mostly there, but I need some one first to
test the .js/.es support and then progress to getting the XHTML support fully
working. I have yet to hear from the submitter reported this issue (#6 Calestyo)

As well as ideas as to what type of sample web pages to to include. I also think
if we are going to go that far, we shuld also provide sample membership,
mailsync, sksconf, DB-CONFIG for both KDB and PTree.

If you have done work with _any_ with database tuning with SKS, or on the
design/shortfalls of our current webpages ( I noticed three relatively common
designd ), or have other ideas to help, please share them with me off-list.

Yaron had a nice piece in ACM Queue on "Why the next language you learn should
be functional": http://queue.acm.org/detail.cfm?id=2038036 The article quickly
moves to Ocaml for examples. Most of SKS in written in Ocaml.

Regards,

- -John
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12-svn5502-2010-12-23 (Windows XP)
Comment: When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
Comment: Be part of the £33† ECHELON -- Use Strong Encryption.
Comment: It's YOUR right - for the time being.
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOmXOjAAoJECMTMVxDW9A0lzAIALtr6iH5CzVkuN+TXQdEpGiE
kk6bjbw5BBnu0nsBsWVhWqO/LgA1RWeDYSfpXO9LVf6yKpIsgU6J/rnvuKizFrxp
mmlhy/q+23YWaWtmD6if4oF5Oh9XWmCUfKqDch9lbTg1lgM0th9zNtvL5xrVHAG3
MU0+ksJSThIpkQ4zilceXH3x6cCqfZn+NGpnn+hA9H1xSdSiBtRLa7xwou7+3buc
HXSb+SCMJfI4/H401anm6McU8Y3/1Fpu9V4snGk4uOKEcMAQ1nvqqL/A/fC9gzX6
xWVxk0bArC8zKIxkp5HY8VNdimti6QviWWE89Gk+q3+4OcL4P/xlpahcWoS+Co+I
XgQBEQgABgUCTplzowAKCRDrXhnz1laYJf3mAQCCT2Rfbcpa0nb73mkVDmtpTLdI
lqzueEOPXbhEyWmnmgD8D2uugu/z3x1LdAG+GH70F/KSrgsOIhFxeG+bDWIrrfA=
=H23e
-----END PGP SIGNATURE-----



reply via email to

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