[development] why locale import is slow and a memory eater?

Gabor Hojtsy gabor at hojtsy.hu
Thu Feb 2 19:33:52 UTC 2006

Dries Buytaert wrote:
> On 30 Dec 2005, at 23:13, Gabor Hojtsy wrote:
>> And here comes the question. Now, if a PO file is broken for any  reason,
>> the real SQL import process is skipped. But whether the file is broken
>> at some point is only possible to tell, if we parse the file up to  that
>> point. If the SQL changes are made incrementally, then the PO file  would
>> end up half-imported. Question is if it is a problem or not. I think
>> this is a minor problem, since you are supposed to upload a  translation
>> which you are about to use, so if your po file is broken it is not a
>> problem that it is half imported, you should fix and try again.
> Good analysis; it matches my own observations.  I don't think a  partial
> import is a problem.  Quite the contrary;

This analysis is now turned into a patch for review. Memory usage
decrease is fantastic, see the chart attached.



More information about the development mailing list