[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgp-keyserver-folk
Subject:    Re: server & network resources used by SKS?
From:       "Yaron M. Minsky" <yminsky () cs ! cornell ! edu>
Date:       2003-07-24 2:02:52
[Download RAW message or body]

SKS resource usage is pretty moderate.  CPU usage is quite low (not in
the top 20 processes on my desktop machine which is also an SKS
server.)  The bandwidth requirements are actually much less than for
running a PKS server, since you effectively receive each key only once,
rather than multiple times.  SKS has two processes, sks_db which is the
basic keyserver, and sks_recon which handles replication.  Each process
takes 15-20 megs of ram as normally configured, though you can reduce
the size of the processes at the expense of slower operation.

y

On Wed, 2003-07-23 at 12:17, Magnus wrote:
> Hello,
> 
> (I am not subscribed to the mailing list and it seems that the listmom 
> would prefer to not permit just any old person to subscribe.  That 
> said, please copy me on responses.)
> 
> I am the PGP keyring maintainer for TriLUG (http://trilug.org).  TriLUG 
> has been blessed to have a lot of hardware donated, as well as some 
> bandwidth and rack space at a co-lo facility.  The hardware and 
> bandwidth availability are not infinite, however, so I wanted to ping 
> y'all and find out what I should expect.
> 
> Can someone enlighten me please as to what sort of machine resources 
> are used by running a public SKS server?  Is it a very demanding 
> service hardware-wise?  I mean, would a lowly Pentium 133 doing nothing 
> else make a fine SKS server or is something more robust called for?
> 
> Also, what sort of bandwidth utilization can be expected from running a 
> public keyserver?
> 
> Thanks
> 
> --
> 
> C. Magnus Hedemark
> http://trilug.org/~chrish
> PGP Key fingerprint = 984D 9A88 3D60 016F BE01 1506 60FB 85E1 9ABD 96F6
-- 
|--------/            Yaron M. Minsky              \--------|
|--------\ http://www.cs.cornell.edu/home/yminsky/ /--------|

Open PGP --- KeyID B1FFD916 (new key as of Dec 4th)
Fingerprint: 5BF6 83E1 0CE3 1043 95D8 F8D5 9F12 B3A9 B1FF D916



[prev in list] [next in list] [prev in thread] [next in thread]