 Show Posts
|
|
Pages: « 1 2 3 4 [5] 6 »
|
|
When I try to import Watching only wallet data from a text file, the file browser freezes. I can't scroll, select files, or even close it.
I happened to be importing another Watching only wallet, after I closed Armory instead of it scanning individual wallets, it started scanning the whole thing, I could not see balances on any wallet as if I had initiated a full rescan.
Also you might want to update the OP with the new testing release (0.92.99.3)
|
|
|
|
Small text bug in Message Signing/Verification and on most tabs such as Transactions, Announcements, etc: http://prntscr.com/5w8qc8On Mac |
|
|
|
Should be tonight. We're wrapping up a bunch of the bugfixes and intermediate testing.
I'm very happy to hear that  |
|
|
|
|
0.92.99.3 is coming either today or tomorrow, correct?
I need the HDD opts ASAP
|
|
|
|
|
Tried build-app.py, Armory builds but closes immediately after I try to run it.
python Armory.app
/usr/local/opt/python/bin/python2.7: can't find '__main__' module in 'Armory.app'
|
|
|
|
|
Yea I'll just go ahead and wait. I was never too good with stuff like that.
PS I'm on Mac
|
|
|
|
Hi everyone, just a quick update: goatpig has created and HDD_optimization branch in the repo, and my first test confirms that it is dramatically better. Once Core was synchronized, it took only about 45 minutes to both build and scan the databases. This is now dramatically faster than the original LevelDB-based implementation of previous versions.
If you are running from the repo, I encourage you to check out the branch and try it. Otherwise, wait a day or two and we'll wrap up this optimization with a bunch of the other bug fixes into a .3 testing release.
The only thing is I can't build from source using the instructions on the website or build-app.py |
|
|
|
Rebuilding DB, but have a backup of my old one. 5 days now  |
|
|
|
|
I hope those HDD opts speed things up good, because the way it seems I might have to rebuild my DB
|
|
|
|
|
It also instantly reads headers from the DB
Question: What does blocks-lock have in it?
|
|
|
|
|
Another thing, do you have an IRC?
|
|
|
|
|
No, my testing release just keeps crashing whenever I bring it online.
It crashes right after this in the log:
-INFO - 1421711289: (BlockUtils.cpp:1236) Loading block data... file 186 offset 83813524
|
|
|
|
You should first wait and see if that code works =P
Right after you posted that Armory had a SIGABRT error and it won't stop doing that *insert worried face here* Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Application Specific Information: abort() called terminating with uncaught exception of type LMDBException: Failed to close env tx (MDB_BAD_TXN: Transaction cannot recover - it must be aborted) |
|
|
|
You sir, along with all Armory devs, deserve a tip  |
|
|
|
|
Receive Bitcoins never ending Loading window is still there
Click on Receive Bitcoins and close it, Loading window with a progress bar doesn't go away until you close it.
|
|
|
|
|
Just saw the HDD Optimization branch, goatpig seems to be working hard! BTC
|
|
|
|
snip
Fullnode will be slow on HDD until I'm done with the current round of optimizations. Ignore supernode on HDDs. There will be a testing release when the changes are solid. Don't toy with the current version if you don't have a SSD.
I'm using an SSHD (hybrid drive) |
|
|
|
|
Is the initial DB build/scan going to be this slow for a while?
I invest in a lot of cloud mining and I need to be able to monitor payments, invest more, etc. with a lot of addresses without having to check each one on blockchain.
|
|
|
|
You are still building the DB (copying block data over), not scanning (actually parsing the transaction data). When scanning supernode, you will be using over 2GB RAM at least.
But why does it use such little resources? That's what I don't understand. About 40% of RAM is free on my system at any given time, why doesn't Armory take it? Same with IO. |
|
|
|
snip
The obvious bottleneck is I/O. Moreover, LMDB maps its whole dataset in RAM, so a machine with little RAM and a swapping file on a HDD will get crushed.
I have 16 GB of RAM and a 1 GB swap file on my SSHD(85 MB/s read/write), it still goes extremely slowly, and I see Armory using ≤41 MB of the swap file and ≤200 MB of RAM. Armory only uses about 1 MB/s of IO right now. |
|
|
|
|
