Dashboard > ApacheDS Addons > ... > Benchmarks > SLAMD Setup
SLAMD Setup
Added by Ersin Er, last edited by Alex Karasulu on Jul 18, 2006  (view change)
Labels: 
(None)


Client Machines

There are 3 separate clients configured for SLAMD. The three clients are fermi, newton, and hertz. All are on a LAN hitting the server machines using a 100 MB connection for maxwell and using a 1 GB connection to connect to pauli (with an exception to hertz).

We are decomissioning newton because it's my primary workstation (causes jitter with use during tests) and using two new boxes, dirac and tesla. Here's what we have now:

Client Load Generators

  • dirac
  • tesla
  • hertz
  • fermi

Servers

  • maxwell
  • pauli

Client Instances

Each client machine is running 3 separate SLAMD client instances which generate load. Unless otherwise stated all tests should use all 9 clients on all client machines with 9 threads per client.

SLAMD Server user accounts

There are 3 groups of users. The admin group, the SLAMDUser group, and other. The admins can change the slamd application settings in tomcat etc. There's only a couple of us in this group. The SLAMDUsers create, add, delete, import and export new job runs, and add new kinds of jobs extending the SLAMD application. The other users of which there is only one, the guest user account, can only view and search for different job runs.

Use guest/guest to gain access to SLAMD Server here:

http://slamd.homeip.net/slamd/ 

LDAP Servers (ApacheDS Addons)
Machine Specifications (ApacheDS Addons)

Site running on a free Atlassian Confluence Open Source Project License granted to Safehaus. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.4 Build:#809 Jun 12, 2007) - Bug/feature request - Contact Administrators