Ingredient assignment in recommendations is incorrect

[inz]

It looks like mapping ingredients back from the MiniZinc model has an issue.

When I generate a recommendation for an instance of the new 'Rails app with PostgreSQL' template (where PostgreSQL master scales vertically, all other components scale horizontally), I get the following recommendations:

The recommendations look sensible overall, but 'Delayed Job Worker' apparently scales vertically instead of 'PostgreSQL Master'.

I think we had a similar issue before, there is probably just an ordering mismatch between generating the model and parsing recommendations.

[joe4dev]

I could reproduce the same behavior and will look into that.

[joe4dev]

Interestingly, this error only occurs at production: https://app.thestove.io I couldn't reproduce this error locally or at staging: http://staging.frontend.thestove.io/ It appears that the order of recommendations is simply reversed (the ratio across instance count is roughly the same):

This image compares production (left) vs staging (right). Notice that production uses pricing data from 1-2 months ago whereas staging is up to date. However, the price difference for Amazon is surprisingly huge 🙄 (945 vs 270)

[joe4dev]

I now updated the pricing data in production and also the dependent admin recommendation seeds. This seems to fix this ordering issue with the production data. The mapping is correct now although the ingredients are displayed in different order in production and staging.

The sanity check (production vs staging) looks fine producing exactly the same results:

[joe4dev]

Newly generated recommendation in production still suffer from the ordering issue. Generating exactly the same recommendation (Rails app with 5k users) as the admin recommendation (created based on admin seeds) after instantiating the Rails template yielded this issue again: