We often get questions from clients about how to handle large amounts of concurrent

users. We do have higher volume clients (north of 1 million users), but know very little

about the server configuration. This is, frankly, not an area of expertise for us.

I'm also attaching some anecdotal information from our internal load testing (done a while ago, but

should apply to most versions of the Engine) Check that out here:
http://docs.google.com/Doc?id=dd2b2ff_0g9m9kzgr.
 

Things we would suggest for high loads would include using SQL Server NOT OPTIMIZED

for the persistence engine (it's actually faster against big loads) and upping the communication

frequency from the default of 10 seconds to about 2 minutes.

If Out of Memory errors occur, be sure to check:

1.  Turn off the ASP.Net trace log...

2.  Check the commit frequency of the content.  You can do this in the SCORMPackageProperties table.  Increase the time between commits,that may help

as well.