How many requests (acquire, validate, invalidate…) can one Clickshare Authentication Server handle per second?
This depends very much on the quantity of “iron” one throws at the problem. Our early experience suggests that one small machine (Intel Pentium, say) can handle about 25 requests per second – or about 1M requests in a (12 hour) day. We have noted that this volume scales well with changes in processor performance probably to the point where throughput is limited by the network interface (ability of the network to deliver packets to the machine’s network adaptor, and the ability of that adaptor to deliver packet’s to the process). Please recall that Clickshare’s “token validation” bears NO resemblence to the “credit card verification” process (where, for each request, a separate call is opened and closed). The Clickshare Authentication Service can be thought of as an “authentication proxy”. The billing entity’s Web Server tells Clickshare: “This is a valid user. Register this user for a new session, and validate all the user’s requests for me (within the confines of service parameters an
