Hi *,
On Thu, Apr 7, 2011 at 10:16 PM, Rimas Kudelis <rq@akl.lt> wrote:
2011.04.07 20:38, Christian Lohmaier rašė:
Thus especially to Friedel and Dwayne and Rimas: Is there a problem with
adding
WSGIDaemonProcess pootle-export threads=3 stack-size=1048576
maximum-requests=5 inactivity-timeout=1200 display-name=%{GROUP}
<Location /*/*/export/zip>
WSGIProcessGroup pootle-export
</Location>
[...]
I like the idea, but I'll leave it to Friedel and Dwayne to judge if it's
problematic or not.
As there has been no reply, I just did add that (with LocationMatch
instead of Location, as it's not just lang/project/export/zip, but
<variable-length>/export/zip) and also limited the number of
concurrent export jobs to 1, (otherwise requesting zips for the same
language and project would consume ~twice the amount of time - if the
user waits until first processing is finished, and then requests the
other zip, the user will get that second zip instantly.
There don't seem to be any drawbacks, so that's the way to go - this
way regular translation will not be blocked/affected by the exporting
blocking all available worker slots or all RAM or all CPU
ciao
Christian
--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Re: [libreoffice-l10n] Pootle migration · Sérgio Marques
Re: [libreoffice-l10n] Pootle migration · Leif Lodahl
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.