How much disk space do you need to work?
-
We regularly run out of disk space on our lixus dev servers as the admin team don't want to put quotas in place. I had a look today and in my 'working' area containing many local checkouts of different things that had been built with all their temp files, log files from running them, the odd core file, etc and I've used 150gb. On my windows machine there's another 20gb of similar stuff. This seems like a lot, how much do others have?
Whatever it is, it's usually not enough. But seriously, my work machine has an 80GB hard drive and I'm constantly having to manage it because it's almost full. Mostly with test and dev tools. I have 1T internal and external hard drives on my home machine and 250GB on my laptop. Much better. Meanwhile, software keeps getting bigger and more resource intensive, so it all seems relative...
-
We regularly run out of disk space on our lixus dev servers as the admin team don't want to put quotas in place. I had a look today and in my 'working' area containing many local checkouts of different things that had been built with all their temp files, log files from running them, the odd core file, etc and I've used 150gb. On my windows machine there's another 20gb of similar stuff. This seems like a lot, how much do others have?
150GB is a bit much, but I wouldn't consider it excessive. I typically keep ~5 complete, compiled source trees around on my dev system, each might be a few GB in size. I find that after about five views, I start to loose track of what changes are in each that make them worth keeping, so I'm pretty aggressive about cleaning up ones I no longer need.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
-
We regularly run out of disk space on our lixus dev servers as the admin team don't want to put quotas in place. I had a look today and in my 'working' area containing many local checkouts of different things that had been built with all their temp files, log files from running them, the odd core file, etc and I've used 150gb. On my windows machine there's another 20gb of similar stuff. This seems like a lot, how much do others have?
I did a very thorough investigation of the space we actively need some 30 months back, when all we had was a 80 GB HD and the option to outsource data to the company network. I've found our disks to be constantly full, and we had to move rather recent packages of data over to the network drives to make do every month or two. Looking at the amount of network space (40 GB and actual local space (75 GB) we needed, plus additional space we'd need due to projects moved from 32bit to 64 bit applications, I estimated our need at that point in time to be around 150-160 GB of space. I even estimated the amount of data adding to that number per year, multiplied it with the average life time of our desktops (about 5-6 years), and ended up with a minimum of 200-220 GB. Today, 30 months later, I am using 165 GB. That's a bit less than anticipated, but that is mostly due to the fact that we haven't yet moved our application to 64 bit. Of course, all these numbers are based on very stable assumptions: working on a single application with a known set of tools and no short term or even mid term plans to radically redesign any parts of it, or launch another project. These numbers include Windows 7, the typical set of office tools, VisualStudio, some more dev tools, some 8-10 working copies of our application that I switch between for different purposes, and a considerable amount of project data that we keep for testing or reproduction of errors.
-
Given that I collect source code like other people collect stamps you really don't want to know and I'm not sure I've ever added it all up correctly, terror bites, as the flea said to the shark.
"The secret of happiness is freedom, and the secret of freedom, courage." Thucydides (B.C. 460-400)
-
My machine currently has a 60gb hard drive...and its running vista and VS 2005 + 08 + 10. I can only fit two repositories on it, and i have about 500mb of free space with that swap file set at a max of 512 (and that never causes problems). Luckily, I'm allegedly getting a new machine next Monday with a 128 GB SSD and 300GB HD.
CPallini wrote:
You cannot argue with agile people so just take the extreme approach and shoot him. :Smile:
Shelby Robertson wrote:
...i have about 500mb of free space with that swap file set at a max of 512...
You get better performance out of a swapfile when it is "large" and not fragmented. Best case is contiguous. The swapfile is not generally used much on a system, but when it is, it is always when the system is really busy, and fragmentation makes the problem(s) worse. Use of an SSD disk will alter the statistics somewhat, but split I/Os (ie. breaking up a "large" I/O into pieces) badly impact the swapping process. SSDs still work better with a contiguous swapfile.
-- Harvey
-
Whew! I assume that this post is the result of large quantities of pizza and beer?
-- Harvey
I assume you are about to expire from boredom if you're reading 10 day old drivel written by some amateur politician who thinks he can write software. :)
"The secret of happiness is freedom, and the secret of freedom, courage." Thucydides (B.C. 460-400)
-
I assume you are about to expire from boredom if you're reading 10 day old drivel written by some amateur politician who thinks he can write software. :)
"The secret of happiness is freedom, and the secret of freedom, courage." Thucydides (B.C. 460-400)
-
Shelby Robertson wrote:
...i have about 500mb of free space with that swap file set at a max of 512...
You get better performance out of a swapfile when it is "large" and not fragmented. Best case is contiguous. The swapfile is not generally used much on a system, but when it is, it is always when the system is really busy, and fragmentation makes the problem(s) worse. Use of an SSD disk will alter the statistics somewhat, but split I/Os (ie. breaking up a "large" I/O into pieces) badly impact the swapping process. SSDs still work better with a contiguous swapfile.
-- Harvey
H.Brydon wrote:
You get better performance out of a swapfile when it is "large" and not fragmented. Best case is contiguous. The swapfile is not generally used much on a system, but when it is, it is always when the system is really busy, and fragmentation makes the problem(s) worse.
H.Brydon wrote:
Shelby Robertson wrote:
...i have about 500mb of free space
If you don't have enough disk space for anything larger, then larger is not better. Also in the particular system we are talking about, the swap file is hit near constantly. Said system needs to be thrown away.
CPallini wrote:
You cannot argue with agile people so just take the extreme approach and shoot him. :Smile:
-
We regularly run out of disk space on our lixus dev servers as the admin team don't want to put quotas in place. I had a look today and in my 'working' area containing many local checkouts of different things that had been built with all their temp files, log files from running them, the odd core file, etc and I've used 150gb. On my windows machine there's another 20gb of similar stuff. This seems like a lot, how much do others have?
I use about 105 gig on my work machine, which includes 14 g of music, plus a bunch of other unnecessary files, and a number of project I have downloaded, either from codeproject, or my own company, that are unnecessary. On my laptop, which I recently had a disk failure, I replaced a 750gb hd with a 250 and currently using only 64 gb. Now on my desktop at home, I am always close to filled because I use it for downloading and ripping, including videos. I have a 4 TB drive in my desktop which I use for all my data, and a 2 TB USB backup which I keep stuff that I really do not want to loose if the 4TB dies (happy it is not a WE since I have had more failures with WE drives). My final backup is a 500 gb, which now does not hold quite as much as I would like. I do not backup the videos. I have seen a lot of stuff on servers at work which should have been removed years ago that is still there. Stuff that may have unintentionally been placed on a server and now cannot be deleted.
-
To work... not much, if we exclude virtual machines, around a 1GB will do it, if I stored every project I worked on in the past, maybe around 10 GB will suffice; however dealing with music and movies, space can go really quick.
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...