8000 Translator performance · Issue #13676 · symfony/symfony · GitHub
[go: up one dir, main page]
Skip to content

Translator performance #13676

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.

Sign up for GitHub

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

Jump to bottom
Closed
theUniC opened this issue Feb 13, 2015 · 6 comments
Closed

Translator performance #13676

theUniC opened this issue Feb 13, 2015 · 6 comments
Labels
Enhancement Performance Translation

Comments

@theUniC
Copy link
theUniC commented Feb 13, 2015

Hi,

I wonder if there is any way to use custom Message Catalogues in the Translator component. I've found that the default implementation is unusable when there are lots of translations (actually, I'm working with ~7 Mb of translation generated files in several locales). I've been googling a lot, but not been able to find documentation regarding this topic.

Thanks.
Christian.
@ghost
Copy link
ghost commented Feb 13, 2015

i think if you could generate a profile with xdebug or xphrof that would probalby help the team figure out the bottlenecks.

@jakzal
Copy link
Contributor
jakzal commented Feb 13, 2015

or... profile your app with blackfire and share the profile with us.

@theUniC
Copy link
Author
theUniC commented Feb 13, 2015

The case is that each time I've to retrieve a translation, the translation service not only loads the validation, form, security and routing translations, but it has to load around ~100Mb of additional translations in memory. Just to retrieve a single translation in a single language. And the application, obviously, runs out of memory.

@Tobion
Copy link
Contributor
Tobion commented Feb 13, 2015

See #2570

@javiereguiluz javiereguiluz mentioned this issue Mar 17, 2015
Closed
This was referenced Mar 19, 2015
Closed
Closed
@aitboudad aitboudad mentioned this issue May 3, 2015
Closed
@aitboudad aitboudad mentioned this issue Sep 30, 2015
Closed
@ostrolucky
Copy link
Contributor

This issue seems outdated, there have already been PRs which improve performance. ping @javiereguiluz

@javiereguiluz
Copy link
Member

OK, let's close as "fixed" ... and we can create new issues for other specific issues about translator performance. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement Performance Translation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@fabpot @javiereguiluz @jakzal @theUniC @ostrolucky @Tobion
0