Three servers, three agents, one controller, one load test. Need a creative solution, or just a really good answer...pardon my ignorance!

Locked Three servers, three agents, one controller, one load test. Need a creative solution, or just a really good answer...pardon my ignorance!

  • Friday, April 13, 2012 9:12 PM
     
     

    I have a global website, not load balanced, but copied and running as separate sites on dedicated servers in three locations around the world. Each server has it's own copy of the website, hosted at it's own URL.  

    http://serverInAsia/myWebSite
    http://serverInAmerica/myWebSite
    http://serverInEurope/myWebSite

    I have agents running on virtual machines on physical machines those same three locations.  The three agents are connected to one controller at my location.

    //agentInAsia     
    //agentInAmerica
    //agentInEurope

    //controllerInAmerica

    I have defined a load test and it runs successfully on the three agents, but since the URL is defined in the load test, all three agents hit only one URL.

    myWebSite.LoadTest

    What I need is a way to set agent to web server affinity. Where each agent hits it's local web server, but all agents are running the same load test.  This is kind f the opposite of IP Switching.  More like programatically setting the target URL for each agent to all use with the one load test. I've also looked at parameterized web servers, but don't know how to access agent properties from the testsettings file, in order to address each agent individually.

    So to restate...

    From the controllerInAmerica, myWebSite.LoadTest runs, which pushes out to the agents.  The agentInAsia runs that test, only against http://serverInAsia/myWebSite, while agentInEurope runs that test, but only against http://serverInEurope/myWebSite, and so forth.

    Any ideas?

    Thanks from Corbo.

All Replies

  • Saturday, April 14, 2012 1:12 AM
     
     Answered

    One of the ways is to set up a geo load balancer which has a vanity url. All agents will hit this url but will in turn be redirected to the nearest deployment.

    http://www.akamai.com/html/solutions/gtm.html

    Thanks,

    Anuj


    http://www.anujchaudhary.com

  • Monday, April 16, 2012 1:58 PM
     
     Answered

    Thank You Anuj,

    I will look into that as a more permanent solution.

    I believe that I have a good temp fix for the purposes of load testing.  I am going to try defining the test with a fake URL, and then create an entry in each Agents host file to point that URL to the appropriate server for the region.  Anyone see any reason what that will not work?  Feel free to post up.

    Thanks from Craig

  • Friday, April 20, 2012 7:37 AM
    Moderator
     
     

    Hello Craig,

    Have you managed to resolve your issue? And does Anuj's reply help you?

    Thanks.


    Vicky Song [MSFT]
    MSDN Community Support | Feedback to us