Apache OpenOffice (AOO) Bugzilla – Issue 69231
Performance issue with creating installation sets
Last modified: 2013-08-07 15:34:42 UTC
The build tree wich serves as an image for the creation of the RPM file is placed on the destination volume in the packaging process. This might be substantial slower than having it on a local (temp) FS if the destination drive for the package is a remote volume. This is especially true of multiple package sets are created from diffrent build machines. Is it possible to create the build tree from which the RPM is made on a temporary FS on the build machine?
Setting target 2.x
It's not only linux & rpm; the same holds true for solaris and creating packages. For solaris we have a second issue: unpacking zip files etc. happens in $tmp. Unfortunately normally this is not /tmp but /var/tmp. /tmp would not only be much faster (because its just RAM instead of hard disk), at least on our RE build machines we also have much more space available on /tmp than on /var/tmp. Having too much pack processess may let '/' run out of disk space - very inconveniant.
Accepted
Set target to 2.3 to have a defined target milestone. If that is too ambitious, please choose another target.
IS -> DV: Please have a look at this.
Changed target
Just out of curiosity: Is the effort so high for this fix? A naive onlooker like me is tempted to think that, at least for the part Rüdiger mentioned, the fix consists of modifying a few directory locations. And it is a pity for Release Engineering that there is not yet a fix available, as the creation of the installation sets could be dramatically improved...
-
Fix not integrated yet, because performance gain is low ( about 10 % ) compared with risk of breaking the packaging process.
solaris issue with /var/tmp versus /tmp is fixed elsewhere. Using $TEMP is fine.
Set new target.