I just had a separate incident. My computer was shut down for a few hours only. It was about 45 blocks behind when Armory was started up again, and it took about 5 minutes per block to update. I closed Armory, opened up Qt to let it update since they both use the same data, and it was finished within a minute or two. Closed Qt to open Armory back up, all is good.
My point was that it would have taken HOURS just to update 45 blocks when Qt did it in minutes. This was an intermittent problem and I couldn't replicate it.
Topic: Armory Startup Proccess (Read 2899 times)
I just notified the same problem, but I didn't update or change the system in any way.
I run Armory 0.92.1 on Ubuntu 13.10.
I run Armory 0.92.1 on Ubuntu 13.10.
The process does seem to take way too long (and much longer than Bitcoin QT) on a regular basis. The blockchain is 100% synced, but "building databases" and "scanning transaction history" sometimes takes a long time, whereas other times it takes 5-10 minutes.
It seems to me as though 5-10 minutes or so is too long, but what do I know. Is there a good reason why Armory takes so long to start compared to other thick wallets?
It seems to me as though 5-10 minutes or so is too long, but what do I know. Is there a good reason why Armory takes so long to start compared to other thick wallets?
I have this same problem. Every time I start Armory it takes anywhere from 15-30 minutes to initialize, sync, and build databases.
- Win 8.1, x64
- Armory and BT Core up to date
- Blockchain stored on an external HD
- 2 wallets; one online encrypted, one Watch Only
- Win 8.1, x64
- Armory and BT Core up to date
- Blockchain stored on an external HD
- 2 wallets; one online encrypted, one Watch Only
I have this same problem. Every time I start Armory it takes anywhere from 15-30 minutes to initialize, sync, and build databases.
- Win 8.1, x64
- Armory and BT Core up to date
- Blockchain stored on an external HD
- 2 wallets; one online encrypted, one Watch Only
anyone else? - Win 8.1, x64
- Armory and BT Core up to date
- Blockchain stored on an external HD
- 2 wallets; one online encrypted, one Watch Only
Which version are you running? Which OS? What are the computer specs? etc.
Version 0.92.1 on Windows 8.1. I have a quad-core intel i7 proccessor, 8gb of ram, and an Nvidia 650m gpu. The disk is slow, I think it's in the 5,000-6000 RPM range.
Yes, I'm having same problem he does. This time, it took only ~30 seconds from start up until I see btc balance. But there are other times where it takes a very long time, like 30 minutes to rescan all the transactions again. I have a fairly fast computer too, on win7 OS.
Which version are you running? Which OS? What are the computer specs? etc.
I'm a little bit confused about what is going on here, every time I start Armory, it remains in offline mode for a long time as it goes through several steps:
1. Initializing Bitcoin Engine
2. Building Databases (Shouldn't this be a one time thing except for any new blocks? Seems to take several hours.)
3. Scan Transaction History (this takes about 45 minutes even if I've only been offline for a day or two).
I don't understand why Armory seems to be redoing all the hard work except for downloading the blockchain every time I start it. Today I started Armory at 9:53am, I'll post the time it completes later so someone can hopefully tell me if this is normal or not.
EDIT: Maybe last time I started it was some kind of error, this time it took under 15 minutes.
1. Initializing Bitcoin Engine
2. Building Databases (Shouldn't this be a one time thing except for any new blocks? Seems to take several hours.)
3. Scan Transaction History (this takes about 45 minutes even if I've only been offline for a day or two).
I don't understand why Armory seems to be redoing all the hard work except for downloading the blockchain every time I start it. Today I started Armory at 9:53am, I'll post the time it completes later so someone can hopefully tell me if this is normal or not.
EDIT: Maybe last time I started it was some kind of error, this time it took under 15 minutes.
Jump to: