-
Notifications
You must be signed in to change notification settings - Fork 75
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
Adding reasonable defaults to our examples for max concurrent units #747
Conversation
@@ -8,3 +8,6 @@ mephisto: | |||
world_file: ${task_dir}/demo_worlds.py | |||
task_description_file: ${task_dir}/task_description.html | |||
num_conversations: 1 | |||
task: | |||
# We expect to be able to handle 25 concurrent conversations without issue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this a typo? Says 25 in the comment but 50 for the value...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
25 conversations, but they require 2 connected people per. I see the comment is misleading here, can make explicit
@@ -8,3 +8,6 @@ mephisto: | |||
world_file: ${task_dir}/demo_worlds.py | |||
task_description_file: ${task_dir}/task_description.html | |||
num_conversations: 1 | |||
task: | |||
# We expect to be able to handle 25 concurrent conversations without issue | |||
max_num_concurrent_units: 50 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
50 here^
Overview
Mostly just the title. As brought up in #746, not having these kinds of defaults means that if people use the default values they're more likely to hit a bad experience (too much server load) rather than be low utilization. To make the basic case better, I've selected some defaults that should be pretty good on this tradeoff (at least until we hit the point that we can use our
metrics
tooling to scale this dynamically... in version 2.0 or something).