Quote:
Originally Posted by FitGirl
Typical urban myth. Browsing the web creates and deletes thousands and millions of files. Reading/writing files is a NORMAL mode for any HDD. Just make defragmentation once a week or so to keep random access at good speed.
|
It may not really be a myth from my point of view, I mean a hard drive is mechanical, there are moving parts and it can be compare best to an engine of a car. What you're saying there "web creates and deletes thousands and millions of files" can be challenged by saying, at what rate does a browser actually create and delete those thousands and million files? I'll take GTAV as an example, way before we had to use rawdet and rawrest, and repacks needed close to 140GB some less just install the game. Now look at that figure, 140GB and how long did the installation take? Hmm, 4 hours at best and a day when installing on slower PCs, don't forget srep virtual temp which can be as big as 10GB. So 140GB or more IO from the repack itself + reflate temps, all that must happen in 4-24 hours, the temperature will obviously increase and stay as high as possible meanwhile things like oil also heat up and a couple of mechanisms that don't like to be run at high revs for a long period of time. Now let's look at browsing, do you really think a browser can do so much IO? The answer is yes, but the question is how frequently must it be used in order for it to match the frequency of a repack installing? Well the answer is a long time, I myself don't even think a browser can make 140GB of IO even in 10 days meaning, yes millions of files will be created an deleted but the hard drive mechanisms will not be over working because at the rate at which they are created an deleted, I mean for example looking for information on wikipedia, I open a page, thousand files are created, it's obvious I opened the page to view information, I read for 20 minutes, IO transfer is very low, because I'm reading something then I say, I'm done reading this, I move to the next page, old files deleted and new files deleted, it's like that, while a repack, whenever it gets the chance to create and delete a file, depending on HDD speed, it will just keep going and going until installation is finished, meanwhile I'm not even done reading my 7th page on the web and total IO is only 33mb. Example, idiot driving from England to France to watch a football game, driving the car to its max vs some guy driving at normal speeds, it's obvious the guy who's driving fast is a repacker and the guy driving slow is a browser, the guy driving fast will mess up the engine because of things like high revs and etc.
Long story short, repacks can actually break HDD because they can actually strain the disk because of rapid activity, there's heat that's generated.
Simple example
https://www.quora.com/How-does-a-hig...ect-the-engine
Temps or not, since a hard drive is not like SSD which has a limit number of writes, The only thing HDD surfers from is it being mechanical but other than that it can probably work forever.