Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Testing RAC performance under load

  • Assumptions:
    • RAC hosts will be hammer and steele

Overall Results Grid

Test 1 (Results)

  • Purpose: To test basic RAC functionality and establish a baseline for comparision
  • DB Configuration
    • Internal Hosts: Hammer/Steele
    • External Hosts: Hammer/Steele
    • Connect Using: LDAP string
    • Internal: Normal Smartsite-Test
    • External: SAK-1202 running on a manually managed tablespace.
    • Special Notes: None
  • Sakai Configuration
    • Tag: TBD
    • Servers: braddock.ucdavis.edu/littlejohn.ucdavis.edu using load balancer smartsite-test.ucdavis.edu
  • Silk Configuration
    • Project: Smartsite-Test RAC
    • Script: SmartsiteViewing.bdf
    • Test Time: 1 hr 15 mins
    • Max Users: 100
    • Workload: Increasing - Starting at 25 increasing 5 users every 15 seconds.
  • Metrics Watched
    • Load on hammer
    • Load on steele
    • Silk Metrics:
      • Transactions OK
      • Average Page Time
      • Requests Sent (Count)
      • Errors
  • Notes: None

Test 2 (Results)

  • Purpose: To test chatting while running on the RAC
  • DB Configuration
    • Internal Hosts: Hammer/Steele
    • External Hosts: Hammer/Steele
    • Connect Using: LDAP string
    • Internal: Normal Smartsite-Test
    • External: SAK-1202 running on a manually managed tablespace.
    • Special Notes: Chat will be fully turned on and maximized on this test
  • Sakai Configuration
    • Tag: TBD
    • Servers: braddock.ucdavis.edu/littlejohn.ucdavis.edu using load balancer smartsite-test.ucdavis.edu
  • Silk Configuration
    • Project: Smartsite-Test RAC
    • Script: SmartsiteChat.bdf
    • Test Time: 1 hr 15 mins
    • Max Users: 100
    • Workload: Increasing - Starting at 25 increasing 5 users every 15 seconds.
  • Metrics Watched
    • Load on hammer
    • Load on steele
    • Silk Metrics:
      • Transactions OK
      • Average Page Time
      • Requests Sent (Count)
      • Errors
  • Notes: After this test is over, the database needs to be cleared.

Test 3 (Results)

  • Purpose: To test RAC failover
  • DB Configuration
    • Internal Hosts: Hammer/Steele
    • External Hosts: Hammer/Steele
    • Connect Using: LDAP string
    • Internal: Normal Smartsite-Test
    • External: SAK-1202 running on a manually managed tablespace.
    • Special Notes: At time + 15 minutes, One of the nodes should simulate a hard down. Pulling the power or pulling the network cables should be sufficient to simulate this. The nodes should be left off during the remainder of the test.
  • Sakai Configuration
    • Tag: TBD
    • Servers: braddock.ucdavis.edu/littlejohn.ucdavis.edu using load balancer smartsite-test.ucdavis.edu
  • Silk Configuration
    • Project: Smartsite-Test RAC
    • Script: SmartsiteViewing.bdf
    • Test Time: 1 hr
    • Max Users: 100
    • Workload: Increasing - Starting at 25 increasing 5 users every 15 seconds.
  • Metrics Watched
    • Load on hammer
    • Load on steele
    • Silk Metrics:
      • Transactions OK
      • Average Page Time
      • Requests Sent (Count)
      • Errors
  • Notes: If Error threshold goes over 10X Test 1(or if test 1 has no errors, 150) Then this test will be terminated and considered to fail.

Test 4 (Results)

  • Purpose: To test RAC long term operation
  • DB Configuration
    • Internal Hosts: Hammer/Steele
    • External Hosts: Hammer/Steele
    • Connect Using: LDAP string
    • Internal: Normal Smartsite-Test
    • External: SAK-1202 running on a manually managed tablespace.
    • Special Notes: None
  • Sakai Configuration
    • Tag: TBD
    • Servers: braddock.ucdavis.edu (pulled from smartsite-test's loadbalancer)
  • Silk Configuration
    • Project: Smartsite-Test RAC
    • Script: SmartsiteViewing.bdf
    • Test Time: 91-96 hours (Thursday Night to Monday Morning
    • Max Users: 100
    • Workload: Increasing - Starting at 25 increasing 5 users every 15 seconds.
    • Possible Workload: all Day - Peaks and valleys occuring 75 minutes. (Ie start with 20 users, 75 minutes later, go to 100, 75 minutes later, drop to 20, rinse/repeat)
  • Metrics Watched
    • Load on hammer
    • Load on steele
    • Silk Metrics:
      • Transactions OK
      • Average Page Time
      • Requests Sent (Count)
      • Errors
  • Notes: Hopefully Silk Central can run this, otherwise we'll have to play it by ear the exact mechanics.
  • No labels