Quote from: goatpig on April 07, 2015, 02:21:52 AM

Quote from: STRML on April 07, 2015, 01:56:28 AM

Anything to be done about armoryd's crazy memory usage? I'm seeing 41GB virt and about 6GB residual. It's causing other processes to start swapping. It is done scanning blocks, this is persistent memory usage. In comparison, bitcoind only uses about 55MB residual.

Restarting the process causes the memory to go down, but then armoryd starts eating up CPU and filling up again. It continually is using the lion's share of resources on the system.

Upcoming DB changes will reduce the memory footprint. For now you should manage BitcoinQt manually so that you can restart Armory after a full rescan without having to restart Core.

In addition, as you've pointed out before, the memory usage is somewhat of a misnomer. If the system needs the memory, Armory will surrender it.