I ran 10 threads each running 100 threads. I get a rate of about 31ms
per loginpage/processLogin/accessCode2Token flow.
According to JProfiler, 65% of time is spent in the password hashing
algorithm. I guess this is not surprising because this password hashing
algorithm is *supposed* to eat up CPU, right?
BTW, running 20 threads concurrently I start to get deadlocks in the
database around UserSession processing. Going to look into that.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com