Issue 69231 - Performance issue with creating installation sets
Summary: Performance issue with creating installation sets
Status: ACCEPTED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-04 09:32 UTC by jens-heiner.rechtien
Modified: 2013-08-07 15:34 UTC (History)
5 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description jens-heiner.rechtien 2006-09-04 09:32:23 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?
Comment 1 ingo.schmidt-rosbiegal 2006-09-04 16:40:57 UTC 
Setting target 2.x
Comment 2 rt 2006-09-04 16:53:43 UTC 
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.
Comment 3 ingo.schmidt-rosbiegal 2006-10-11 11:07:46 UTC 
Accepted
Comment 4 epost 2007-01-18 12:49:00 UTC 
Set target to 2.3 to have a defined target milestone. If that is too ambitious,
please choose another target.
Comment 5 ingo.schmidt-rosbiegal 2007-03-12 14:19:11 UTC 
IS -> DV: Please have a look at this.
Comment 6 dirk.voelzke 2007-03-14 14:14:53 UTC 
Accepted
Comment 7 dirk.voelzke 2007-06-14 08:30:47 UTC 
Changed target
Comment 8 epost 2007-06-15 16:45:15 UTC 
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...
Comment 9 epost 2007-06-15 16:46:11 UTC 
-
Comment 10 dirk.voelzke 2007-07-02 08:29:42 UTC 
Fix not integrated yet, because performance gain is low ( about 10 % ) compared
with risk of breaking the packaging process.
Comment 11 rt 2007-11-07 08:20:40 UTC 
solaris issue with /var/tmp versus /tmp is fixed elsewhere. Using $TEMP is fine.
Comment 12 dirk.voelzke 2007-12-03 09:29:28 UTC 
Set new target.