Interesting. Thinking about it I suspect the GUI may not handle that many addresses that well though of course an exchange would use a headless node.
Do you notice slowness during any particular action?
Nothing that is unworkable. But here are a few notes:
- Slowness happens when generating the addresses, and CPU usage goes up / fans start up, etc.
- Slowness also occurs when it is the end of the 2 hours distribution period and balances are being processed
- During that "processing" period (probably in another thread) I also get unresponsiveness, such as:
- transfers go on hold until processing is done
- RPC commands are just blocked until processing is done
- quitting the GUI just "hangs" until processing is done
I'm just thinking if I was an exchange, I'd need a receive address per account, so I'd have to have them pre-generated, or generate on the fly. Either way, it seems generating an address requires some CPU power by itself. (Does it have some PoW associated with it, to prevent address spam?)
Yea that sound like a suspect, the PoW that's used to prevent transaction spam. Are you running it inside a VM? Possible 1 CPU core? In your config.json what does it list for work_thread and io_thread count?