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

Performance optimization #82

Closed
sswaroopgupta opened this issue May 28, 2018 · 5 comments
Closed

Performance optimization #82

sswaroopgupta opened this issue May 28, 2018 · 5 comments
Assignees

Comments

@sswaroopgupta
Copy link
Contributor

Expected behavior
The performance of the ruby language runner must be comparable to js/python language runners

Actual behavior
The performance of gauge-ruby on Linux OS is slow

Steps to replicate

The performance of the runner is slow compared to js/python language runner

Version

Gauge version: 0.9.9.nightly-2018-05-24
Commit Hash: 2150e31

Plugins
-------
ruby (0.5.1.nightly-2018-05-23)
@sswaroopgupta
Copy link
Contributor Author

The performance of ruby runner on Linux should be comparable with its performance on OSx

@sriv
Copy link
Member

sriv commented May 29, 2018

Setting TCP_NODELAY helps speed up execution in linux. Fix should be available in nightly >= 29/5/18

@sswaroopgupta
Copy link
Contributor Author

sswaroopgupta commented May 29, 2018

Ruby Performance test suite takes more than 5 minutes to execute where as Python Performance test suite takes 5 seconds

Observed on VM Ubuntu
CPU - 2 cores
Memory - 2GB

Version

Gauge version: 0.9.9.nightly-2018-05-24
Commit Hash: 2150e31

Plugins
-------
ruby (0.5.1.nightly-2018-05-29)

@sriv
Copy link
Member

sriv commented May 30, 2018

This project has Gemfile.lock checked in, causing the gauge-ruby dependency to be fixed at revision 690b36679a5b3cd9941aaa73a716c8a56541693a which is older than the revision that has the fix.

Run bundle update and then run bundle exec gauge run specs and see if it makes any difference.

@sriv sriv added ready for QA and removed ready labels May 30, 2018
@sswaroopgupta
Copy link
Contributor Author

@sriv Thanks. Works as expected after bundle install

@ghost ghost removed the ready for QA label May 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants