PhantomJS kills server - too many processes?

[trashymctrash]

Hello everyone,

I integrated Rspec tests (with Capybara) with PhantomJS in our Jenkins CI system. They are triggered after each deploy to a staging system, and only one job can run at the same time.

Sysadmins contacted me today and told me that it is very likely that these tests cause a really high load on the Apache server and basically killed one of them. Apparently one single test has caused 400 processes on three servers.

My questions (I am not a sysadmin, so some of them might sound stupid):

- Is that scenario even possible?

- Can I limit the amount of requests in PhantomJS somehow?

- Has anyone experienced similar issues?

Basically, the tests do normal stuff: buy a product and go through checkout, write a review for a product, nothing fancy. Definitely no load tests or stress tests.

If further info is needed, I'll be happy to provide.

Thanks in advance

[James Greene]

I'm not sure what's happening in your RSpec, Capybara, or Jenkins pieces but PhantomJS itself just runs a single process unless your Phantom script explicitly creates more with the "child_process" module.

Sincerely,
    James Greene

--
You received this message because you are subscribed to the Google Groups "phantomjs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phantomjs+...@googlegroups.com.
Visit this group at http://groups.google.com/group/phantomjs.
For more options, visit https://groups.google.com/groups/opt_out.

[trashymctrash]

Turns out it was a server issue. Thank you for your input, James.

[James Greene]

Glad you were able to get it resolved.

Sincerely,
    James Greene
    Sent from my [smart?]phone