In fact it is completely impracticable to do this.
128 thousand indices in an array, is a large amount to be manipulated and / or compared.
The ideal is to keep such information in the database and to look for it based on a minimum parameter limit.
I have maybe two solutions:
Physical Archive
This array is kept as a physical file (which extension you want, in json format)
[EDITED] Idea
Just as an add-on, in your case, I think it's better to create a file for each "letter" of the alphabet.
Unless your comparison, include values between the value of the array, for example: ada
- ada
- adá
- guava fruit
- giraffe (joking, haha)
With this I believe that the search is faster (in a single file), but of course, increase the number of requests on the server, and to help in this case, leave any information in the inline (minify) / strong>, so that the size is reduced / compressed to the maximum.
Cached page (json / xml)
I do not like and / or recommend xml, but feel free
Have a page (route) of your system / site, which contains this array also in json format, however, such a page will be cached by the time you set.
In this way, when other applications access the specific page (for example, http://www.examplo.com.br/ptbr.json
or http://www.examplo.com.br/ptbr.php
- the extension itself does not matter, but how you will handle the request), you return this page, which in this if it is cached, it will not load again.
Doubt
Do you use any frameworks? The vast majority of them already have a ready cache system, and excellent administration of the extension / response / protocol type of your request / route.
Some links to help you
I hope I have helped.