Quote from: grondilu on November 23, 2010, 05:35:32 PM

Quote from: farmer_boy on November 23, 2010, 05:29:25 PM

Running bitcoin feels like its indexing my harddisk. I will probably stop running the client, because of that. I don't mind the CPU usuage, but its seek behaviour is ridiculous. Isn't there some way to keep more in memory data structures and only write them to disk when the program is stopped or when there is a lot of date to write?

What are the harddisk requirements anyway?

I'm not sure I understand your pb correctly but... I guess you could make a symlink from a virtual fs to $HOME/.bitcoin, and crontab a backup of your wallet.

To do that one needs to know the requirements of the application. I was suggesting to put this logic into the application, but it appears that after running it for some time, it stopped attacking my harddisk. It's now just frying my CPUs, but that's ok.

I would like to know what it was doing to my harddisk before. I suppose it is some kind of syncing to the rest of the nodes, getting a semi-complete history of the network?