user12211: It is said in the bitcoin wiki that:

The accounts code does not scale up to thousands of accounts with tens of thousands of transactions, because by-account (and by-account-by-time) indices are not implemented.
  So many operations (like computing an account balance) require accessing every wallet transaction.

so my question is, what solution would be acceptable to implement a program who would be in charge of thousands of account (like an e-wallet).
My first guess would be to run multiple bitcoind instances, in order to keep the account by daemon ratio under a certain limit.
Any other idea ?

user11761: Several options:

Don't use bitcoind
Use bitcoind to interface the p2p network but ignore accounts and other abstractions
Hack bitcoind to use by-account indices


12211: <p>It is said in the <a href="https://en.bitcoin.it/wiki/Accounts_explained" rel="nofollow">bitcoin wiki</a> that:</p>

<blockquote>
  <p>The accounts code does not scale up to thousands of accounts with tens of thousands of transactions, because by-account (and by-account-by-time) indices are not implemented.
  So many operations (like computing an account balance) require accessing every wallet transaction.</p>
</blockquote>

<p>so my question is, what solution would be acceptable to implement a program who would be in charge of thousands of account (like an e-wallet).</p>

<p>My first guess would be to run multiple bitcoind instances, in order to keep the account by daemon ratio under a certain limit.</p>

<p>Any other idea ?</p>
 11761: <p>Several options:</p>

<ul>
<li>Don't use bitcoind</li>
<li>Use bitcoind to interface the p2p network but ignore accounts and other abstractions</li>
<li>Hack bitcoind to use by-account indices</li>
</ul>
