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

Have you compared the Locust with the Tsung? #377

Closed
likezjuisee opened this issue Jan 20, 2016 · 3 comments
Closed

Have you compared the Locust with the Tsung? #377

likezjuisee opened this issue Jan 20, 2016 · 3 comments

Comments

@likezjuisee
Copy link

I have compared them ,and the result is Tsung is more better. Especially in RPS. PS. the test environment is the same. 32G mem and 8 CPUS.

@heyman
Copy link
Member

heyman commented Jan 20, 2016

Hardware is cheap compared to developer time. Locust's goal is to be able to simulate real user behaviour by writing python code (and not XML), and then simulating lots of these users using the system. "Recording" sessions doesn't always cut it.

If Tsung solves your use-case in a better way than Locust, I recommend that you use it.

@heyman heyman closed this as completed Jan 20, 2016
@likezjuisee
Copy link
Author

thx.
one more question, why do you choose the requests, pycurl maybe is better than this.

@heyman
Copy link
Member

heyman commented Jan 20, 2016

Because requests provides the best API. It's quite simple to use some other client lib with Locust if one wants to (see http://docs.locust.io/en/latest/testing-other-systems.html).

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

2 participants