From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UiOSV-0001XF-SV for bitcoin-development@lists.sourceforge.net; Fri, 31 May 2013 12:29:27 +0000 X-ACL-Warn: Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1UiOSU-00006R-Sw for bitcoin-development@lists.sourceforge.net; Fri, 31 May 2013 12:29:27 +0000 Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id DE4C2209B3 for ; Fri, 31 May 2013 08:10:50 -0400 (EDT) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute2.internal (MEProxy); Fri, 31 May 2013 08:10:50 -0400 X-Sasl-enc: Veojjz91FMMKTmSm1oR1AWvkZ5wB6Ar9uSKu6h7+bkIY 1370002250 Received: from mail-vc0-f180.google.com (unknown [209.85.220.180]) by mail.messagingengine.com (Postfix) with ESMTPA id A8366C8014A for ; Fri, 31 May 2013 08:10:50 -0400 (EDT) Received: by mail-vc0-f180.google.com with SMTP id gd11so973066vcb.39 for ; Fri, 31 May 2013 05:10:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hS+H3zNb/gndH8QKykX8ArPqfw/C/ZDnGLGGopXfL90=; b=pRdInzJmXYEqHqjrb2+yDXqlrS4owcMAk/+p3hVVH9k81r20b1GHP8SCCVgPXo9K5+ npaI4TzdJRYEX6t86cP1CJKYX00T9gxtlfas1g1PKGMMkyviRsAXMgWUNlZ1fwS5vQ49 TPr/KmPBxZXUYVUEkymYIFoX34T8cqGwkBMOrGE2hjxOuZ6E+0xQcYrRy1IKiOHWytdp jV+wcFQzLhX8XAOIX60+qeBHmiRS3pH9LdPV9qrVYqkJ1ipbJ6YKs8iGaqcec2QAyd1R 3zzynBNy5hCp/t6ByQT1N1QMF6y3VWiADjvY+3eOyDETksQYBuip0rzh1k9Hmpb755Go yLew== MIME-Version: 1.0 X-Received: by 10.58.200.131 with SMTP id js3mr9939715vec.33.1370002250447; Fri, 31 May 2013 05:10:50 -0700 (PDT) Received: by 10.58.254.4 with HTTP; Fri, 31 May 2013 05:10:50 -0700 (PDT) In-Reply-To: References: Date: Fri, 31 May 2013 06:10:50 -0600 Message-ID: From: Michael Hendricks To: =?UTF-8?Q?Rune_Kj=C3=A6r_Svendsen?= Content-Type: multipart/alternative; boundary=047d7bd6b2da7ac6f304de028123 X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1UiOSU-00006R-Sw Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Implementing batch processing for -blocknotify 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: Fri, 31 May 2013 12:29:28 -0000 --047d7bd6b2da7ac6f304de028123 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, May 31, 2013 at 5:56 AM, Rune Kj=C3=A6r Svendsen wrote: > I have an application that wants to keep up with new blocks as they come > in. For that I can use the -blocknotify option with bitcoind, which will > execute my application for each new block. > > The problem is that my app isn't necessarily quick enough to finish its > work before a new block comes in and the app is executed again. > In a similar circumstance, I changed my -blocknotify script to quickly append necessary information to a queue and immediately exit. A separate script runs at all times monitoring this queue for work and performs the labor intensive calculations. I hope that helps. --=20 Michael --047d7bd6b2da7ac6f304de028123 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Fri, May 31, 2013 at 5:56 AM, Rune Kj=C3=A6r Svendsen <= span dir=3D"ltr"><runesvend@gmail.com> wrote:
=
I have an application = that wants to keep up with new blocks as they come in. For that I can use t= he -blocknotify option with bitcoind, which will execute my application for= each new block.

The problem is that my app isn't necessarily quick enough to= finish its work before a new block comes in and the app is executed again.=

In a similar circumstance, I c= hanged my -blocknotify script to quickly append necessary information to a = queue and immediately exit. =C2=A0A separate script runs at all times monit= oring this queue for work and performs the labor intensive calculations.

I hope that helps.

--=C2=A0
Michael
--047d7bd6b2da7ac6f304de028123--