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

Add support to configure the number of browser processes per instance. #12

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

adam-hampton-sp
Copy link

Modifies AwsVmManager in the following ways:

  • CHROME_THREAD_COUNT becomes non-final.
  • FIREFOX_IE_THREAD_COUNT becomes non final.

New values are applied at runtime if the awsProperties contain keys
like:

  • node_max_processes_chrome=8
  • node_max_processes_firefox=1

Modifies AwsVmManager in the following ways:
 - CHROME_THREAD_COUNT becomes non-final.
 - FIREFOX_IE_THREAD_COUNT becomes non final.
 
New values are applied at runtime if the awsProperties contain keys
like:
 - node_max_processes_chrome=8
 - node_max_processes_firefox=1
// Allow the user to override the default settings for browser
// processes per EC2 operating system instance.
String maxChromeThreads = awsProperties.getProperty("node_max_processes_chrome");
if ((null != maxChromeThreads) && (0 != maxChromeThreads.length())) {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A better check is !StringUtils.isEmpty(maxChromeThreads)

@mhardin
Copy link
Owner

mhardin commented Apr 21, 2017

@adam-hampton-sp are you able to add unit tests around the new logic you added?

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

Successfully merging this pull request may close these issues.

2 participants