Bitcoin wallet performance

[djeZo]

I am running service of renting mining rigs and have BTC wallet running to receive payments from customers and send them on to mining rig providers.

Every new customer gets new deposit BTC address, so these are being created quickly. There are a lot of customers that only registered but will most likely never upload any BTC or use the service. I was thinking about purging them, but BTC wallet has no option to "forget" certain account with address - it stays there forever.

I have 2 questions regarding that;

1. Should I use "generate deposit address" method, rather than automatically creating new deposit address upon registration to minimize number of "forever empty" accounts?

2. How much of accounts can BTC wallet (I use bitcoin-qt) actually take before this effects performance drastically. How should be BTC wallet run on such server? In GUI mode (does it have any performance hit)?

[djeZo]

Noone knows? 

[djeZo]

Keypool? Are there some more references about this. I checked all official pages and not much is said on exactly how bitcoin client should be run when dealing with auto-payments.

[djeZo]

Keypool? Are there some more references about this. I checked all official pages and not much is said on exactly how bitcoin client should be run when dealing with auto-payments.

https://en.bitcoin.it/wiki/Key_pool

There is no correct way to run the bitcoin client when being a merchant, it is trial and error that works best for you.

OK. Well, so far, everything is working great with no performace issues, but my goal is to reach 10 times as much traffic and volume and I do not want to hit some problems at that point.
Keypool, as it looks, would be only useful if I had no backup established. But I do - I backup wallet every time new address is generated.

[djeZo]

Keypool? Are there some more references about this. I checked all official pages and not much is said on exactly how bitcoin client should be run when dealing with auto-payments.

https://en.bitcoin.it/wiki/Key_pool

There is no correct way to run the bitcoin client when being a merchant, it is trial and error that works best for you.

OK. Well, so far, everything is working great with no performace issues, but my goal is to reach 10 times as much traffic and volume and I do not want to hit some problems at that point.
Keypool, as it looks, would be only useful if I had no backup established. But I do - I backup wallet every time new address is generated.

If you backup every address then that isn't helping you, you should just backup after the keypool has been hit. Keypool is useful if you hit your keypool size a lot. If you plan on doing 10 times of traffic, then you will need to increase your key pool size. It is a feature that many people don't tune, but can help a lot.

Yes, I understand, but my service is not doing exchanges - new address is generated possibly maybe every 10 minutes, not more often.

[djeZo]

I am doing database backup anyway, so this should not be an issue.