Hey folks,
I have some questions on which I need some pointers.
First, -nodiskptree: To my understanding this would result in longer
startup-times, more memory consumption but faster lookups. So the ptree
is generated, but kept in ram. Final analysis: Enabling this option
would speed up lookups
Hi Christian,
thank you for offering the dumps! :-)
About the -nodiskptree option... please correct me if I am wrong,
but wouldn't the operating system's disk reading cache render this
option useless? At least it seems to be like this on my Kubuntu
desktop - with sufficient free memory, I can
On 11.02.2014 08:38, Christian Reiß wrote:
[...]
Also I am using puppet to deploy the sks server. Anyone else using
puppet? membership file (et all) is managed over hiera. So if we have
any puppet3 users I am glad to share.
Lastly, I wrote a (10 liner) php-script that queries the
sks-keyserver
On 02/11/2014 10:48 AM, Kristian Fiskerstrand wrote:
By default stats are updated once a day, for more than this you need
to send a USR2-signal to sks.
In particular, you need to send USR2 to sks db, not sks recon. And
note that while sks db is calculating stats, it cannot serve HKP
requests.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/11/2014 04:53 PM, Daniel Kahn Gillmor wrote:
On 02/11/2014 10:48 AM, Kristian Fiskerstrand wrote:
By default stats are updated once a day, for more than this you
need to send a USR2-signal to sks.
In particular, you need to send USR2 to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am 11.02.2014 16:59, schrieb Kristian Fiskerstrand:
On 02/11/2014 04:53 PM, Daniel Kahn Gillmor wrote:
On 02/11/2014 10:48 AM, Kristian Fiskerstrand wrote:
By default stats are updated once a day, for more than this you
need to send a
On 02/11/2014 01:58 PM, Benny Baumann wrote:
Am 11.02.2014 16:59, schrieb Kristian Fiskerstrand:
Unless you run it in a clustered setup where the different members
calculate it on different times and the frontend passes the request on
before timeout :p
Its almost instantly for my maschine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/11/2014 08:19 PM, Daniel Kahn Gillmor wrote:
On 02/11/2014 01:58 PM, Benny Baumann wrote:
Am 11.02.2014 16:59, schrieb Kristian Fiskerstrand:
Unless you run it in a clustered setup where the different
members calculate it on different
Hi there,
Quoting Daniel Kahn Gillmor d...@fifthhorseman.net:
On a pretty decent machine (zimmermann.mayfirst.org), i'm seeing the
following duration in the logs:
2014-02-11 19:17:17 Calculating DB stats
2014-02-11 19:17:49 Done calculating DB stats
so that's over half a minute of blocked
Hi,
Am 11.02.2014 20:19, schrieb Daniel Kahn Gillmor:
On 02/11/2014 01:58 PM, Benny Baumann wrote:
Am 11.02.2014 16:59, schrieb Kristian Fiskerstrand:
Unless you run it in a clustered setup where the different members
calculate it on different times and the frontend passes the request on
On 02/11/2014 02:19 PM, Daniel Kahn Gillmor wrote:
On 02/11/2014 01:58 PM, Benny Baumann wrote:
Am 11.02.2014 16:59, schrieb Kristian Fiskerstrand:
Unless you run it in a clustered setup where the different members
calculate it on different times and the frontend passes the request on
before
* Sebastian Wiesinger sks-de...@ml.karotte.org [2011-12-05 22:12]:
Hi,
I'm setting up sks 1.1.2 with bdb 4.8 on a Debian 64bit Box.
Any specific tuning ideas for the database (or other parts as well)? I
want to get it right and I'm confused what to do to get the best
performance out of
12 matches
Mail list logo
