Hi,
Between the signer starts the timer and stops the timer, the following
actions are being done:
- queue RRsets for signing
- do sign operations
- check whether all appointed jobs have been successful
I argue the latter action can be done after stopping the timer. So there
is some overhead/offset, although 2 minutes seems excessively large.
Also interesting to see is your signing times. I see STATS lines every
5-15 minutes. And every line a lot of RRSIGs are being renewed. I am
curious how your key and signing policy (kasp) looks like for this zone,
or what commands you are performing that result in this behavior.
Best regards,
Matthijs
On Tue, 31 Jul 2012, Yuri Schaeffer wrote:
Hi Stuart,
On 07/31/2012 12:06 PM, 刘硕 wrote:
I'm signing a 200Mb zone example4 and I find that the avg of signing
speed varies , [..]
I do not know enough of the signer to answer your questions but if you
plot RRSIG_new with RRSIG_time in a graph you'd see a quite linear
function. It does have an offset of about 2 minutes for your zone on
your machine, independent of how many signatures need to be generated. I
don't know where this constant overhead is coming from but I think that
skews the displayed average. About 1300 sig/sec seems a better
estimation for your machine.
Regards,
Yuri
_______________________________________________
Opendnssec-user mailing list
[email protected]
https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
_______________________________________________
Opendnssec-user mailing list
[email protected]
https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
