Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VQldR-0005f0-0w for bitcoin-development@lists.sourceforge.net; Mon, 30 Sep 2013 22:08:09 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.173 as permitted sender) client-ip=209.85.217.173; envelope-from=gmaxwell@gmail.com; helo=mail-lb0-f173.google.com; Received: from mail-lb0-f173.google.com ([209.85.217.173]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VQldQ-0002ct-Bl for bitcoin-development@lists.sourceforge.net; Mon, 30 Sep 2013 22:08:09 +0000 Received: by mail-lb0-f173.google.com with SMTP id o14so5136416lbi.32 for ; Mon, 30 Sep 2013 15:08:01 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.152.29.103 with SMTP id j7mr21343595lah.7.1380578881546; Mon, 30 Sep 2013 15:08:01 -0700 (PDT) Received: by 10.112.89.72 with HTTP; Mon, 30 Sep 2013 15:08:01 -0700 (PDT) In-Reply-To: References: Date: Mon, 30 Sep 2013 15:08:01 -0700 Message-ID: From: Gregory Maxwell To: =?UTF-8?Q?Fatima_Castiglione_Maldonado_=E5=8F=91?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gmaxwell[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1VQldQ-0002ct-Bl Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] bitcoind stops responding X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Sep 2013 22:08:09 -0000 On Mon, Sep 30, 2013 at 3:00 PM, Fatima Castiglione Maldonado =E5=8F=91 wrote: > I am new on the list. I got a similar problem. > If I put "sendToAdress" transactions to bitcoind, it will accept between = 1 > and 3 transactions per minute, depending on the underlying machine. > If I try to send one transaction every 20 seconds or less, bitcoind stops > responding to RPC calls. > > Does anybody know of any solution / fix / workaround for this? This is unrelated to Slush's question. The complexity of IsConfirmed/Ismine is exponential and starts taking tens of seconds at a chain of a dozen unconfirmed transactions (and growing from there) There are some patches that change this, but since the whole network will only average about 7tx per second, you're probably doing something wrong if you're building great big chains of unconfirmed transaction. Are you aware of sendmany?