Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Load testing a site whose domain name is not pointed/registered . #326

Closed
rjdp opened this issue Aug 21, 2015 · 1 comment
Closed

Load testing a site whose domain name is not pointed/registered . #326

rjdp opened this issue Aug 21, 2015 · 1 comment

Comments

@rjdp
Copy link

rjdp commented Aug 21, 2015

I tried putting entry in /etc/hosts for the site but , the request were going to original site . I will explain with an example:

  • Lets my site name google.com(mentioned as argument to server_name directive in vhost's nginx configuration) hosted on a vps with IP abc.efg.ijk.lmn
  • In my /etc/hosts I have put an entry abc.efg.ijk.lmn google.com .
  • I have abc.txt file in htdocs of my site google.com, and I am able to access it using google.com/abc.txt .

I have task in my locust taskset that is programmed to hit google.com/abc.txt

but when i run locust --host=http://google.com

but request is going to THE google.com

any help would be greatly appreciated

@mthurlin
Copy link

mthurlin commented Feb 9, 2016

Locust uses gevent internally, and I know gevent has been having issues with DNS previously (pre 1.0):
http://www.gevent.org/whatsnew_1_0.html#new-dns-resolver

These should have been fixed with gevent 1.0, but you can try setting the environment variable:

GEVENT_RESOLVER=ares

and see if that helps.

You could also try making request with/without gevent from the python REPL to see if there is any issues there, or if it is related strictly to locust

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants