You'll usually never notice this with just one hard drive import going, but if you have twenty different download queues all competing for database access and individual 0.1-second hits of heavy CPU work, you will discover your client starts to judder and lag. It also takes a decent whack of CPU to import a file. If you can realistically only archive/delete filter 50 files a day, there is little benefit to downloading 500 new files a day.
Figure out what workflows work for you, how fast you process files, what content you actually want, how much bandwidth and hard drive space you have, and prioritise and throttle your incoming downloads to match. Many users get overexcited with their new ability to download 500,000 files and then do so, only discovering later that 98% of what they got was junk that they now have to wade through. It is very important that you take this slow.
0 kommentar(er)
