Matjaž Horvat
Matjaž Horvat
Note that the change needs to happen on both, backend and frontend.
Upgraded plan on prod to Standard 2 today. Let's observe how that affects the cache hit rate and the overall performance.
Let's close it. Bumping the plan clearly improved the hit rate and the next DB plan is much more expensive. The best next step for further increasing the hit rate...
Pushed to stage for final testing.
> Submitting empty plural variants should be prohibited: > https://mozilla-pontoon-staging.herokuapp.com/sl/all-projects/all-resources/?status=translated&string=66626 This still needs to be fixed.
> @mathjazz I'm not certain, but should we revert the changes made in #3615 once this lands? Yeah. Can you please include that in this PR?
@eemeli Is the next step here to create another data migration, which will convert regular spaces back to non-breaking spaces based on the non-breaking space presence in the `TranslationMemoryEntry` table?
> The likely next step after that will be introducing the new data model in parallel and as write-only, next to the current models. Once that's in place, it should...
We're essentially hitting #2263 here (see the Traceback below). In addition to fixing the underlying backend problem with the stats (tracked by #2263), we should also make the frontend more...
Running `update_stats(project)` fixed the stats, so approving should work.