since there has been no response on #260 i want to open a new issue to investigate high load of foreman process.
could you give me any pointers on what to do?
see my comment here: #260 (comment)
some more infos:
patchlevel: "2012-10-12 revision 37165"
full_version: "ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-darwin11.4.2]"
gem list foreman
*** LOCAL GEMS ***
redis_server: redis-server config/redis/development.conf
web: bundle exec unicorn -c config/unicorn/development.rb
elasticsearch: elasticsearch -f -D es.config=es/config/elasticsearch.yml
nginx: /usr/local/sbin/nginx -c config/nginx/development.conf -p $PWD/
@phoet Please, check out #303.
@fxposter i'm having a look and will report back to you
looks good for first minutes, will have a look how this works out in the long run
looks like this is only an issue on osx lion. developers with mountain lion do not have this issue in our dev team.
It depends on what services are you running from foreman and how do they behave with their stdout.
what are you referring to? the services are listed above and the whole dev team uses these settings.
In my case it was mongodb. Maybe you have different versions of these services amongst your team.
so you think that this pull request is not needed, because it might be an issue of one of the services?
It is not an "issue" - if service closes it's stdout - foreman should handle it correctly.
Fix #299 and #260
Some processes close their output channels and IO.select keeps
returning them as "readable", while IO#gets returns nil on them, thus
spending a lot of CPU looping through the same reader continuously