An open discussion list for topics related to the eduGAIN interfederation service.

[Mads Freek Petersen <freek AT wayf.dk>]

> On 26 Mar 2019, at 19.27, Peter Schober <peter.schober AT univie.ac.at> wrote:
> 
>> 5.   Specific HSM requirements for
>> 
>> a.   Cryptographic performance;
> 
> With MDQ (siging several thousand[1] of small text files individually,
> instead of signing one ~50MB file) on the horizon that's increasingly
> going to be a factor. You'd want those thousands of signature ops to
> be performed at least daily, possibly more often.
> 
> Personally I think resigning everything in eduGAIN would probably work
> up to 3 or 4 times the number of entities of the current eduGAIN
> aggregate (with 15-20k signing ops taking a few hours) even when using
> smartcard-based HSMs (that typically have a signing performance around
> 1-2 signature operation per second) but views will widely differ here
> across federations.

Just for comparison we do 70 2K signings per second on our Luna boxes from a 
single threaded PHP program using a pyeleven like webservice. So we currently 
sign about 6300 (eduGAIN + WAYF) entities in about 90 seconds. From a 
multithreaded program we can do 2400 signings per second - 1200 on each box.

-Mads

Mads Freek Petersen
Developer
freek AT wayf.dk
+ 45 25 27 80 61

WAYF, Danish e-Infrastructure Cooperation
DTU Asmussens Alle Building 305 |  DK-2800 Kgs. Lyngby, Denmark