ES45 outperforming GS1280 - Tru64 5.1B

From: Jonathan Williams (jonathw_at_shubertorg.com)
Date: 06/23/05

  • Next message: Dave Sill: "Administrivia: Tru64-UNIX-Managers information and policy statement" 
    Date: Thu, 23 Jun 2005 12:32:37 -0400
To: tru64-unix-managers@ornl.gov

    I was told to send out the following:

    We are running IDS 9.40.FC5 and have the following 3 Alpha Tru64 systems
    with Unix 5.1B, Patch Kit 4.

    Royale: GS1280
    8 - 1.3 EV7 CPU's
    8 - gigs of memory

    Broadhurst: ES80
    8 - 1.0 EV7 CPU's
    8 - gigs of memory

    Majestic: ES45
    4 - 1.25 EV6 CPU's
    8 - gigs of memory

    We have a multi-tier in house application so the database never has more
    than 95 connections.
    We use processor affinity (1-7 for 8 cpu and 1-3 for 4 cpu).
    The systems are connected with a gigabit switch (Cisco 4006).

    When using different configurations, the resulting throughput speed makes no
    sense to us.

    1) Royale application server - Majestic db server - fastest combo
    2) Broadhurst application server - Majestic db server - 2nd fastest
    3) Royale application server AND db server - much slower than the previous 2
    configurations
    4) Broadhurst application server - Royale db server - slower than
    configuration #3

    At all times the systems are at least 50% idle and usually 75% idle when
    volume is heavy and timing tests were done.
    All timings done with the exact same physical disks (2 spindles in a SAN we
    configure to the db server).

    We would have thought that configuration 3 would be by far the fastest.
    We notice 'delays' when it appears that IDS completely stops for 4 or 5
    seconds with configuration 4, but only 1 second
    with configuration 3. 'Delay' is defined as all our applications stop (even
    dirty read only) like they are all waiting for the db. There are more
    delays than checkpoints.

    It appears to us that Royale runs slower and communicates slower than
    Majestic when it is a db server but is much faster than Majestic as an
    application server.

    Does anyone have any ideas why our fastest, newest computer Royale would run
    slower than the 4 cpu with slower CPU's?

    Thanks in Advance

    Jonathan Williams
    UNIX Systems Admin.
    The Shubert Organization, Inc.

  • Next message: Dave Sill: "Administrivia: Tru64-UNIX-Managers information and policy statement"

    Relevant Pages

    • SUMMARY: ES45 outperforming GS1280 - Tru64 5.1B
      ... IDS 9.40.FC5 is Informix Dynamic Server (we aren't ... some changes to the Informix configuration file (that didn't have any ... Royale application server AND db server - much slower than the previous 2 ...
      (Tru64-UNIX-Managers)
    • Re: SBS SP 1 installation error
      ... Component Name: Microsoft Exchange Forest Preparation ... Component Name: Server Configuration ... Component Name: Windows Server 2003 Configuration ... Component Name: Networking Configuration ...
      (microsoft.public.windows.server.sbs)
    • Re: SBS 2003 Misconfigured?
      ... The netgear has a setting for the Internet IP which is set to the ... DNS server address is set to SBS server's ip 192.168.5.109 ... but something else is clearly awry if you can't get DHCP ... Which, based on the configuration you gave, is part of the problem. ...
      (microsoft.public.windows.server.sbs)
    • Re: SBS 2003 Misconfigured?
      ... The netgear has a setting for the Internet IP which is set to the ... DNS server address is set to SBS server's ip 192.168.5.109 ... DHCP working - and as Cliff says, that should be a simple thing. ... Which, based on the configuration you gave, is part of the problem. ...
      (microsoft.public.windows.server.sbs)
    • RE: ceicw fails every time
      ... I'd like confirming CEICW steps with you to ensure there is not problem ... You have to rerun the CEICW to make sure your SBS 2003 server have right ... On the "Services Configuration" page, select all the items and then ... Calling CCertCommit::ValidatePropertyBag ...
      (microsoft.public.windows.server.sbs)