Just to give you an idea of RSA calculation in h/w, this is what I get when I run openssl speed test. As per the documentation, the authentication rate should also reflect that, but the real numbers are nowhere close to this. # openssl speed -engine dataplane rsa2048 engine "dataplane" set. Doing 2048 bit private rsa's for 10s: 1125 2048 bit private RSA's in 7.76s Doing 2048 bit public rsa's for 10s: 2027 2048 bit public RSA's in 9.89s OpenSSL 0.9.8p 16 Nov 2010 built on: date options:bn(64,32) md2(int) rc4(ptr,char) des(idx,cisc,16,long) aes(partial) idea(int) blowfish(ptr) compiler: CFLAGS available timing options: TIMES TIMEB HZ=100 [sysconf value] timing function used: times sign verify sign/s verify/s rsa 2048 bits 0.006898s 0.004879s 145.0 205.0 Anurag -----Original Message----- From: Verma Anurag-VNF673 Sent: Friday, December 17, 2010 4:54 PM To: 'FreeRadius developers mailing list' Subject: RE: Performance issue with Freeradius (2.1.7) running Veriwave Alan,
On the same machine? Or on completely different hardware? Good point. It was on a different machine. Let me check the configuration.
Do you know *why* they failed? That question might be interesting to answer.
How do I find that. Running radiusd -X in debug mode slows it down. Is there anyway I can debug this further?
Since you haven't said *anything* about your system, I have no idea. I am not sure if I can disclose that, but the point is that I see the same performance number when done with Microsoft AAA server for a single authentication request. I forgot to mentioned that earlier.
Well... your CPU is really not powerful enough to do RSA. Don't blame FreeRADIUS. Use a faster CPU.
Well, the CPU is not doing it, RSA calculation is offloaded to hardware. So, not sure how faster CPU will help. Anurag