> Jason Self wrote: >> >> I'm looking to setup a FOSSology instance for the gNewSense GNU+Linux >> distro. I was... shocked... shall i say, when i heard the memory >> requirement: A fossology db for their upcoming release (version 3.0, >> code-named metad) would be about 8GB. >> >> Since it'll be a multi-user installation with different people working >> on simultaneously working on different aspects, will FOSSology try to >> hold the entire database in memory? If so I need to get a different >> machine as the one I was planning to use maxes out at 8GB of RAM and >> I'd like something that can be used without swapping. >> >> Plus I read somewhere that FOSSology itself needs ~2GB ram iirc to run >> well so I should be adding this on top of the database requirement?
On Fri, Feb 12, 2010 at 9:34 AM, Mark Donohoe <[email protected]> wrote: > > Jason, > > I'm not sure where you are getting this information. We have set up a > working system on a laptop with 2gig of memory. We don't hold the db in > memory... plus our db only contains the meta-data about the files uploaded. > The unpacked files are kept on the file system and are referenced from > there. > > As far as the next release, we don't have a code name.... and it will be > release 1.3. I'm a developer on the project so I hope I would know about > these things! :-) Can you give me a pointer to where you read this? Hey Mark... Looks like there was some miscommunication. I wasn't talking about the next version of FOSSology being 3.0. Rather, I was talking about setting up a FOSSology instance for the developers that are working on the gNewSense GNU+Linux distribution. It would analyze their repositories, etc. for their next version (and THAT next version is 3.0, code-named metad.) Sounds like something got mixed up there in reading my email. :) As to the 8GB I wasn't referring to the files it analyzed (I assumed that the uploaded files were stored on disk), but rather the FOSSology database itself. Where did I get the information about the database being so large? I was talking with one of the gNewSense developers earlier and that is where I got that when they set up a FOSSology instance for testing (I think sometime in 2009, with version 1.0) and fed their entire repository to FOSSology for analysis, the FOSSology database containing the meta-data about the files uploaded ended up being ~8GB. The disk space requirement was also large, but I don't remember that as well (for a full Debian repo the number was > 1TB) due to extracting every archive of every sort (deb/tar/cpio etc) into individual files and indexing them. I think you've answered my question, though, about memory usage: As long as that entire 8GB database containing the meta-data about the files uploaded isn't going to be held in RAM while the system is running and going about its business I think my current setup will be able to handle it. _______________________________________________ fossology mailing list [email protected] http://fossology.org/mailman/listinfo/fossology
