friendrelop.blogg.se

Softperfect ram disk cant mount
Softperfect ram disk cant mount










softperfect ram disk cant mount

I haven't looked into why, but I'm guessing it's to do with flushing or caching or something. You can see both FC runs are two spikes and it reports it is completed after the first.

softperfect ram disk cant mount

More analysis would be needed to work out exactly what is causing the difference.įirst, it looks like after FastCopy reports it is finished there is still a blip of disk activity a second or two later. There are some other things we could speed up (some risky, some not none would make a huge difference on their own) but it looks like diminishing returns at this point.Īnother observation: When source & dest drive are the same, the speeds become more equal. We could provide options to let you tweak how often the progress dialog updates (in case I was too conservative in how much the updates are throttled), or in how large the inter-thread queues can grow, but I don't personally think that is worth it. Much of that is done on separate threads but there is still an overhead in sending messages between threads, and we don't let the inter-thread queues grow too large or become too out of sync as that can cause other problems. But it does not seem massively faster, and there are inevitably overheads when Opus is doing more with both its UI and in terms of logging, tracking changes (updating collections, etc.), handling a lot more flexibility, etc. So I agree that in this case of thousands of tiny files, FastCopy is a bit faster than Opus (with my configuration at least I didn't try tweaking buffer sizes and non-buffered I/O settings, which I note that FastCopy uses). The time/clock difference are small here.) (Keep in mind the width of this is just a few seconds.












Softperfect ram disk cant mount