Finally, I know why OpenOffice loads as fast as a mammoth runs. According to this interview, this is mainly because the kernel I/O schedulers and readahead algorithm suck, and also because of g++ which sucks at linking.
Pardon, mais LOL.
OpenOffice « performance »
Vous pourriez aussi lire...
Articles
3 réponses
Laisser un commentaire
Ce site utilise Akismet pour réduire les indésirables. En savoir plus sur comment les données de vos commentaires sont utilisées.
no. It is Jesus….
According to its size I guess a mammoth is running faster as you think :)
i suggest a real method to increase performance of OpenOffice. the only way out is DOCK TO TRAY. by using kdocker or alltray.
but there is a difficulty. in manual mode (when you by using mouse indicates window) kdocker succesfully kick openoffice window to tray, but through command line it did not work by default. the solution is to define window ID of opened OpenOffice window and transfer it to kdocker.
here is script that you need put in $HOME/.kde/Autostart/office-to-tray.sh
#!/bin/bash
/opt/openoffice.org2.4/program/scalc -norestore &
sleep 15
/usr/local/bin/kdocker -w `/usr/X11R6/bin/xwininfo -root -children -tree | /bin/grep « OpenOffice.org Calc » | awk ‘{ print $1 }’` &
/opt/openoffice.org2.4/program/swriter -norestore $HOME/.1.doc
sleep 5
/usr/local/bin/kdocker -w `/usr/X11R6/bin/xwininfo -root -children -tree | /bin/grep « .1 – OpenOffice.org Writer » | awk ‘{ print $1 }’` &
and you need put small simple .1.doc file to $HOME.
the result: celeron 1800,512Mb,FC4,KDE , xls file 450kb open for 5 seconds!
and if use icewm even 4 seconds:)