Hi Konrad, By memory you mean disk storage space. The 10x highly depends on the structure of the uploaded data. For example, let’s say you upload a tar file that contains 1000 individual source files. In this case the storage requirement will be 2X the tar file because fossology will store the original tar file plus the 1000 source files. The 10X estimate is based on archives (like tar files or iso’s) containing nested archives. All these files remain in the file repository after the scan is complete because when you are looking at scan results we let you drill down into the actual file contents themselves. For example, if we report that a files has a "GPL-2.0+:3.0” license (that means it contains parts GPL-2.0 or later license and parts of GPL-3.0), then you will probably want to look at the license in the file itself. By keeping the contents of the files after they are scanned, we can do that.
Bob On May 15, 2014, at 8:23 AM, Konrad Urbanski <[email protected]> wrote: > Hello Robert, > Once more question: > the memory required for uploaded source code to the fossology it is 10 x of > uploaded data, is it: > 1. during the fossology scanning process (and it is free memory after > finished)? or > 2. also this amount of memory is required after scanning process finished?
_______________________________________________ fossology mailing list [email protected] http://lists.fossology.org/mailman/listinfo/fossology
