Hi Alexandro,
Thanks a lot for sharing this info.
Currently, I feel the most critical cause of Pootle slowdown is that
Pootle processing itself for handling large files. And find ways to
improve the performance of the processing.
However, obviously, it is worthwhile to try all the possibilities. :)
Thanks again,
Aijin
Alexandro Colorado wrote:
I know php memcache can work magic.
On Tue, 19 Feb 2008 04:26:35 -0600, Aijin Kim <[EMAIL PROTECTED]> wrote:
Hi Pootle users,
In these days, Pootle has been often slowdown. It is mainly because of
CPU overload on the server machine.
The contents for OO.o -especially helpcontents- are very huge. If
several users simultaneously work on line, CPU usage sometimes reaches
100% and the server doesn't accept a new request until it's available
again. Especially executing functions (e.g.,search or get statistics)
with a whole project consumes a lot of resource.
There would be two ways to be considered for the performance
improvement:
1. Increase resource
- upgrade hardware
2. Decrease workload of the server machine
- Apply software patches
- Install some additional software to aid Pootle processing
We're trying to find any possibility to resolve this issue and going to
apply some of them to the server machine soon. I hope those tries can
provide better performance, however I'm not sure yet how much will the
performance are improved.
As I mentioned above, OO.o content itself is huge, therefore it may
naturally take much resource/long time.
So when you work on Pootle, it'd be worthwhile to try to execute
functions with a small unit (per one folder or one file) rather than
whole project. It may give better performance not only to you but also
other users.
I'll keep update you on the further progress.
Thanks,
Aijin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
