service: react-render
runtime: custom
env: flex

# TODO(jlfwong): Figure out what the right scaling policy is
automatic_scaling:
  min_num_instances: 1
  max_num_instances: 200
  cool_down_period_sec: 60
  cpu_utilization:
    target_utilization: 0.4

resources:
  cpu: 1
  # TODO(benkraft): This feels like more memory than we should need!
  memory_gb: 3
  disk_size_gb: 10

service: react-render
runtime: custom
env: flex

# TODO(jlfwong): Figure out what the right scaling policy is
automatic_scaling:
  min_num_instances: 1
  max_num_instances: 200
  cool_down_period_sec: 60
  cpu_utilization:
    target_utilization: 0.2

resources:
  cpu: 1
  # TODO(benkraft): This feels like more memory than we should need!
  memory_gb: 3
  disk_size_gb: 10

Update target CPU use to 20%.
Update target CPU use to 20%.

The react-render server is not scaling to handle the load of the video
page. With recent changes to the way we do SSR, it's bound on network
and/or memory, not CPU. In flex, we cannot sale based on the concurrent
connections or memory, so this sets the target CPU to about what it is
when the server is running as fast as it can.

https://khanacademy.slack.com/archives/C3UDL9QN7/p1537387282000100

Auditors: amos, benkraft
