Quote:
Originally Posted by kovidgoyal
The problem is the writing to dropbox, which takes a long time, I've actually moved that into a separate thread, so the problem should go away.
|
Using dropbox doesn't intrinsically slow down the write operations to the filesystem. It does slow down the processor. The dropbox daemon wakes up for every file, chatters over the network, computes a send package, and then sends it. All of this takes reasonable CPU and I/O bandwidth.
On windows, dropbox also (I think) inserts itself into the notify chain, which means that touching a file will wake up the daemon, consuming yet more cycles.
I turn off dropbox when I am making a big change, such as restoring my library, running calibre2opds, or adding lots of books. The daemon really gets in the way, otherwise, making the operations take significantly longer. I turn it back on when I am done with the large updates.