Hello Bob, Thanks for the detailed information. We will try out "Upload from URL or "Upload from server" options and keep you posted if any queries/issues.
Best regards Kotrappa. From: Gobeille, Robert [mailto:[email protected]] Sent: Thursday, February 13, 2014 9:49 PM To: Kotrappa DeverShetty (WT01 - Manufacturing & Hi Tech) Cc: Matt Germonprez; [email protected]; Akanksha Singh (WT01 - Manufacturing & Hi Tech); Ravishankar T.S (WT01 - Manufacturing & Hi Tech) Subject: Re: [FOSSology] What is the maximum file size Fossology Supports? Hi Kotrappa, That 700 MB limit is a php limit. This is for "Upload from File". You can change that in your php.ini file. See: http://www.fossology.org/projects/fossology/wiki/SysConfig Yes, FOSSology can take larger files with "Upload from URL" or "Upload from Server". 6 or 10 GB is not a problem. The amount of time FOSSology takes to scan such a large upload is highly dependent on your hardware and what has been previously scanned. For example, I just looked at a recent Android scan we did (3.65 GB) and there were about 1.2 million files. However, only 244k files had to be scanned because the other million had already been scanned in previous uploads. Looking at our logs I see nomos scanning at from 9 to 42 files/second. The wide disparity will be due to the complexity of the files and the system load at the time. You should also know that nomos is single threaded, it only does one file at a time. However, our job scheduler does not have this limitation. So if you break your 10GB upload into two 5 GB uploads and submit them both at the same time, they can process in parallel. For doing large uploads (6-10 GB) a dual core 4GB with 200GB HDD won't work very well. A 10 GB upload, after you unpack all the zip files and tar files can easily be over 100GB and you are talking about millions of files that have to be cataloged in the database. The 4GB of RAM is fine for doing scans, but once you start doing reports and Postgres starts joining tables with millions of records, you are going to be starved for memory. It will work, but will be slow. My first recommendation is to use a much bigger server. However, if that is not a possibility you could use our agents (ununpack, license, copyright) stand alone. That way they won't write to the database. Of course, without the database, you will not be able to use the fossology GUI for reports. http://www.fossology.org/projects/fossology/wiki/Using_FOSSology_from_the_Command_Line Bob Gobeille On Feb 13, 2014, at 6:27 AM, <[email protected]<mailto:[email protected]>> <[email protected]<mailto:[email protected]>> wrote: Hello Bob, Matt, We know that FOSSology supports maximum file size that can be uploaded and scanned is 700 MB. But if a big chunk of zip file say around 6GB to 10Gb is uploaded to webserver ( say local apache webserver), Can FOSSology take the URL of webserver with the big file and scan whole 6GB or 10GB? How does FOSSology perform, does it take large amount of time? 1-2 days? For this big file size scanning, do we need high configuration system? Say around 4GB RM, dual core processor, 100-200GB HDD? The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
_______________________________________________ fossology mailing list [email protected] http://lists.fossology.org/mailman/listinfo/fossology
