Best practise project/component size

[eschumacher-99]

Hello,
I would like to know what's the best size for projects and components on Weblate.
Currently, I have one project with 4 components that each hold 20.000 strings and 27 languages.
Everytime I click on a component, it takes about half an hour for it to parse the xliff file and show up on my screen.
This happens since around version 4.2 or 4.3 I believe.
Is there any way to avoid this or is it better to split it into more and therefore smaller components?
Would that change anything?

[github-actions]

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you!

[nijel]

Everytime I click on a component, it takes about half an hour for it to parse the xliff file and show up on my screen.

There is no file parsing going on when displaying the page, it has to be something else causing this delay.

What can be lengthy is updating stats, but this is cached and should not happen that often.

What version do you currently use?

[eschumacher-99]

What version do you currently use?
I'm using Version 4.3

[nijel]

I think there were some slight changes in 4.4, but I don't think it will make a major difference.

When starting with an empty cache, calculating the stats take 4-8 database queries per translation. This should be needed only for changed translations, and it is pre-calculated in the background. If massive changes are going on in all the translations, it will definitely have measurable impact.

In case it happens to you regularly, it would be interesting to figure out why it happens.

[nijel]

@eschumacher-99 I did answer it there, and I don't see how it is related to this issue...

[eschumacher-99]

I looked it up and this is the part that causes the problem. base contains the whole xliff file and this method gets called everytime you click on the project.

diff --git a/formats/ttkit.py b/formats/ttkit.py
index 19b0f86..fb09758 100644
--- a/formats/ttkit.py
+++ b/formats/ttkit.py
@@ -369,7 +369,7 @@ class TTKitFormat(TranslationFormat):
         if not base:
             return monolingual and cls.new_translation is not None
         try:
-            cls.parse_store(base)
+            #cls.parse_store(base)
             return True
         except Exception:
             report_error(cause="File parse error")

[nijel]

It really shouldn't, can you please try whether upgrading addresses it?

[nijel]

Hmm, looking at the code it can indeed happen in some situations...

[nijel]

#5153 should address the issue I've found (it's not yet tested, waiting for CI to run the tests)

[github-actions]

Thank you for your report, the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

[eschumacher-99]

#5153 should address the issue I've found (it's not yet tested, waiting for CI to run the tests)

Thank you very much!