Hopefully a CPU will blow up and save us from manicminer. In the meantime, there's the "ignore" button.
? 
Topic: Is the Qt client killing the hard drive slowly? (Read 2074 times)
Disclaimer: don't use these for any serious stuff - I am not responsible for destroyed wallets or exploded CPU's.
Well.
Use it on testnet and help creating some feedback for sipa and the other devs Well.
Hopefully nothing will blow up.
Disclaimer: don't use these for any serious stuff - I am not responsible for destroyed wallets or exploded CPU's.
Well.
Use it on testnet and help creating some feedback for sipa and the other devs Well.
Hopefully nothing will blow up.
Disclaimer: don't use these for any serious stuff - I am not responsible for destroyed wallets or exploded CPU's.
Well.
Use it on testnet and help creating some feedback for sipa and the other devs Well.
Current versions of the reference client indeed causes excessive disk I/O. The next version (0.8, not yet released) should improve upon this significantly (it uses a more modern database engine, and a new database layout).
sounds very good, the excessive disk usage of the 0.7 release is terrible on older hardware.
you can help test it too: https://bitcointalksearch.org/topic/experimental-pre-08-builds-for-testing-129861
Disclaimer: don't use these for any serious stuff - I am not responsible for destroyed wallets or exploded CPU's.Well.
Use it on testnet and help creating some feedback for sipa and the other devs
.Btw.: I think this thread should not be called is the Qt client, but better "the reference client", as bitcoind behaves just the same afaik.
Dia
you can help test it too: https://bitcointalksearch.org/topic/experimental-pre-08-builds-for-testing-129861
Disclaimer: don't use these for any serious stuff - I am not responsible for destroyed wallets or exploded CPU's.Well.
The next version (0.8, not yet released) should improve upon this significantly (it uses a more modern database engine, and a new database layout).
Does it mean a new database download? Cool, when it will be released?Current versions of the reference client indeed causes excessive disk I/O.
Only when downloading the database or for normal use as well?The next version (0.8, not yet released) should improve upon this significantly (it uses a more modern database engine, and a new database layout).
Does it mean a new database download? Cool, when it will be released? 
I'm just asking this because I read it downloads much faster on an SSD. Even much faster on a RAM disk. I have an older machine. I download the chain for 5 days. Does the downloading process or simply operating the client kill the hard drive?
No. Hard drives are designed to be used as hard drives, which is exactly what you are doing when using the computer with a hard drive. I hope this is clear enough.
Or for GPUs, a GPU used lightly should fetch a higher price than a GPU which mined for the past 3 years. They are otherwise identical, but one has more "wear."
Why would a hard drive be any different?
There is some normal wear of mechanical components with use, and this will eventually lead to failure. Before this point is reached, however, other causes may and do trigger failures: abuse, mechanical shocks, ESD, thermal stress cycles, dusty or smoky environment, etc. The probability of most of these does not increase with use. Failure due to thermal stress is in fact more likely in systems subject to on/off cycles (less use!) than those that are constantly turned on.
Unlike GPUs or HDDs, internal combustion engines are mainly mechanical devices, with rather violent vibrations and stress in normal use, so wear and tear may in fact be a dominant mechanism of failure.
Whether this effect is significant with current usage pattern of bitcoin-qt is not something I can readily answer. It also depends greatly on the specific drive. Some drives park their heads when not actively seeking to spare the wear&tear of the heads hovering close to the platters. Constant usage can interfere with this endurance feature in various ways; it can prevent the heads from ever being parked, or worse, it can create repeated park/unpark operations, for which the drive is only rated for a certain number.
With SSDs there is the well-known write endurance problem, and excessive random write operations can degrade the drive's write performance.
Current versions of the reference client indeed causes excessive disk I/O. The next version (0.8, not yet released) should improve upon this significantly (it uses a more modern database engine, and a new database layout).
Clear enough!
I'm just asking this because I read it downloads much faster on an SSD. Even much faster on a RAM disk. I have an older machine. I download the chain for 5 days. Does the downloading process or simply operating the client kill the hard drive?
No. Hard drives are designed to be used as hard drives, which is exactly what you are doing when using the computer with a hard drive. I hope this is clear enough.
Or for GPUs, a GPU used lightly should fetch a higher price than a GPU which mined for the past 3 years. They are otherwise identical, but one has more "wear."
Why would a hard drive be any different?
There is some normal wear of mechanical components with use, and this will eventually lead to failure. Before this point is reached, however, other causes may and do trigger failures: abuse, mechanical shocks, ESD, thermal stress cycles, dusty or smoky environment, etc. The probability of most of these does not increase with use. Failure due to thermal stress is in fact more likely in systems subject to on/off cycles (less use!) than those that are constantly turned on.
Unlike GPUs or HDDs, internal combustion engines are mainly mechanical devices, with rather violent vibrations and stress in normal use, so wear and tear may in fact be a dominant mechanism of failure.
I'm just asking this because I read it downloads much faster on an SSD. Even much faster on a RAM disk. I have an older machine. I download the chain for 5 days. Does the downloading process or simply operating the client kill the hard drive?
No. Hard drives are designed to be used as hard drives, which is exactly what you are doing when using the computer with a hard drive. I hope this is clear enough.
Or for GPUs, a GPU used lightly should fetch a higher price than a GPU which mined for the past 3 years. They are otherwise identical, but one has more "wear."
Why would a hard drive be any different?
There is some normal wear of mechanical components with use, and this will eventually lead to failure. Before this point is reached, however, other causes may and do trigger failures: abuse, mechanical shocks, ESD, thermal stress cycles, dusty or smoky environment, etc. The probability of most of these does not increase with use. Failure due to thermal stress is in fact more likely in systems subject to on/off cycles (less use!) than those that are constantly turned on.
Unlike GPUs or HDDs, internal combustion engines are mainly mechanical devices, with rather violent vibrations and stress in normal use, so wear and tear may in fact be a dominant mechanism of failure.
I'm just asking this because I read it downloads much faster on an SSD. Even much faster on a RAM disk. I have an older machine. I download the chain for 5 days. Does the downloading process or simply operating the client kill the hard drive?
No. Hard drives are designed to be used as hard drives, which is exactly what you are doing when using the computer with a hard drive. I hope this is clear enough.
Or for GPUs, a GPU used lightly should fetch a higher price than a GPU which mined for the past 3 years. They are otherwise identical, but one has more "wear."
Why would a hard drive be any different?
^ if downloading the blockchain kills your harddrive, your harddrive was probably at the end of it's life anyway.
I'm just asking this because I read it downloads much faster on an SSD. Even much faster on a RAM disk. I have an older machine. I download the chain for 5 days. Does the downloading process or simply operating the client kill the hard drive?
No. Hard drives are designed to be used as hard drives, which is exactly what you are doing when using the computer with a hard drive. I hope this is clear enough.
I'm just asking this because I read it downloads much faster on an SSD. Even much faster on a RAM disk. I have an older machine. I download the chain for 5 days. Does the downloading process or simply operating the client kill the hard drive?
Jump to: