| [orion-dev] Stress-testing the Orion server |
|
I know the server component of Orion is perhaps not
the main focus, but I've elaborated two scripts: 1. A script that will create random user accounts until interrupted. 2. A script that, if given a user list file, will log in, create a workspace if none already exists, fetch all the available files and folders and until interrupted, perform any one of six random actions. Those actions are: - Get a random file - Open a random directory - Get the 'export' version of a directory or project (zip) - Create a file in a random directory - Edit an existing file (download a file, add 6KB of random content, then save it) - Create a new folder somewhere in the tree Here are my questions: 1. If anyone interested in these two scripts? If so, where should I put them? 2. I've created a test instance of an Orion server on Eclipse.org hardware. Unlike the "real" orion.eclipse.org, this test instance has 14 additional CPU cores and a total of 8GB of RAM. Is anyone interested in observing a stress-test of the server while I bombard it with multiple parallel processes of the #2 script above? This would simulate dozens, hundreds, and thousands of concurrent users actively using the server. I would perform this test tomorrow morning (Eastern time). For what it's worth, on the test system I can happily create 5 accounts/second with no noticeable impact on the UI. The manage-users.html page, however, becomes unhappy with thousands of accounts. Denis |