-
Notifications
You must be signed in to change notification settings - Fork 0
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
User range recommendations; Fixes #177 #178
Conversation
I started implementing the corresponding frontend parts.
|
Separates the construction (generate the MiniZinc model) from the evaluation.
Updating the user workload (i.e., `num_simultaneous_users`), updating the dependent constraints, and constructing the MiniZinc model for a certain workload needs to happen atomically. Otherwise, concurrent range construction jobs could interfere with each other.
f3ed913
to
88405f7
Compare
Works for me with the latest version and also with some legacy db dumps I migrated for testing purpose. Should be ok but might need some more testing with concurrent executions (as stated in the PR tasks) |
* Prefer `trigger_range` now * Including adjusted test cases. These now combine vertical and horizontal scaling.
Not needed because the number of simultaneous users is only relevant when generating new recommendations. Therefore, the number of simultaneous users should not be statically assigned to an application ingredient (via the user_workload)
Looks ready to merge for me now |
Add user range support as described in #177
Maintains the existing behavior when triggering single recommendations.
Range generation now separates constructing (i.e., generating the MiniZinc model) from evaluation. See 17a99c0 for more detail.
http://localhost:3000/ingredients/:id/recommendations_completed
works consistently; check concurrent execution with multiple workersDependency: Already rebased on PR #176