# Do all the locale scripts have to run on install and upgrade?
**URL:** https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346
**Category:** Support
**Created:** [14 בפברואר, 2017, 9:24am UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346 "2017-02-14T09:24:21Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@Alexander\_Wright](https://meta.discourse.org/u/Alexander_Wright)
#### Post date: [14 בפברואר, 2017, 9:24am UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346/1 "2017-02-14T09:24:21Z")
Running all the locale scripts seems to take a long time when installing or upgrading.
Is it possible to restrict the set of locales that are installed?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [14 בפברואר, 2017, 10:47am UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346/2 "2017-02-14T10:47:54Z")
I wish it would skip these files too. I think we need to replace Sprockets before we can do that right @sam?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [14 בפברואר, 2017, 12:02pm UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346/3 "2017-02-14T12:02:45Z")
Sort of, the trouble is that when locale is switched in admin we would have to compile an asset conditionally, this would add a reasonable amount of complexity
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [14 בפברואר, 2017, 3:25pm UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346/4 "2017-02-14T15:25:21Z")
Why not compile all languages every time that setting is changed?
Then at least you pay the penalty at time of switch rather than all the time forever and constantly…
---
### Author:  [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [14 בפברואר, 2017, 3:31pm UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346/5 "2017-02-14T15:31:50Z")
Another alternative is to only compile the set locale at rebuild and run a background task to compile the others? (no idea if this is feasible, just a thought that ran through my mind)
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [14 בפברואר, 2017, 3:47pm UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346/6 "2017-02-14T15:47:13Z")
> [@codinghorror](#):
>
> Why not compile all languages every time that setting is changed?
It is doable but has risks, for one we don’t have a system that is able to do any background work on site setting change and notify UI when done (double needed when user locale is enabled), I would hold off on all engineering here till we get rid of sprockets.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [14 בפברואר, 2017, 4:09pm UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346/7 "2017-02-14T16:09:33Z")
Another option is env variable that must be set for any locale other than English, so we can skip all that work unless env is set. Maybe ask user at command line if they plan to ever use any other langs.
---
### Author:  [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [14 בפברואר, 2017, 6:23pm UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346/8 "2017-02-14T18:23:27Z")
> [@sam](#):
>
> get rid of sprockets.
A bit off-topic
I won’t concern myself with worrying about my seeing these
```plaintext
DEPRECATION WARNING: Sprockets method `register_engine` is deprecated.
Please register a mime type using `register_mime_type` then
use `register_compressor` or `register_transformer`.
https://github.com/rails/sprockets/blob/master/guides/extending_sprockets.md#supporting-all-versions-of-sprockets-in-processors
```
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [2 במאי, 2019, 1:47pm UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346/9 "2019-05-02T13:47:06Z")
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2 במאי, 2019, 11:04pm UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346/10 "2019-05-02T23:04:25Z")
This is still the source of much pain and makes rebuilds very slow due to all the locales that sites are not using, but yet _every single locale_ has to be processed on every rebuild @sam.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2 במאי, 2019, 11:05pm UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346/11 "2019-05-02T23:05:22Z")
Yes, I am bumping this to the front of @pmusaraj list next week. We have many plans of improving this and got to make it happen.
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [10 במאי, 2019, 7:42pm UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346/13 "2019-05-10T19:42:20Z")
Locales are still being compiled on rebuild, but the process is now faster due to some improvements in how they are compressed (which was taking the most time on rebuilds). On the most basic DO instance, for example, precompiling each locale takes less than 0.1 seconds now.
Rebuilds are now about [25% faster](https://meta.discourse.org/t/how-much-is-discourse-affected-by-a-faster-cpu/58407/37), on my test DO instance the rebuild takes 4m50s (compared to about 7m previously).
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [10 במאי, 2019, 7:42pm UTC](https://meta.discourse.org/t/do-all-the-locale-scripts-have-to-run-on-install-and-upgrade/57346/14 "2019-05-10T19:42:25Z")