From: Mike Hearn <mike@plan99•net>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Large backlog of transactions building up?
Date: Sun, 23 Sep 2012 14:12:58 +0200 [thread overview]
Message-ID: <CANEZrP2r6sVC_63xx6U7XLbFkukrFEhq-mGAse3vHJ6nf3Q1cw@mail.gmail.com> (raw)
Has anyone got long term longs that contain the pool size and timestamps?
Unfortunately I forgot to enable timestamps in the logs for my own
nodes (the privacy benefit of disabling this by default is
questionable, imho). But just looking at the general trends and
cross-checking against my own memory it definitely seems that there
are more and more pending transactions that don't get cleared into
blocks.
One of my nodes now routinely has 4000 transactions in the mempool.
Blocks typically clear only a few hundred at most, which is what you'd
expect given current transaction rates (around 300 per ten minute
interval). So what are the other pending transactions doing and why
aren't they getting drained out of the mempool?
next reply other threads:[~2012-09-23 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 12:12 Mike Hearn [this message]
2012-09-23 20:30 ` Jeff Garzik
2012-09-23 20:44 ` Gregory Maxwell
2012-09-23 21:54 ` Mike Hearn
2012-09-25 17:34 ` Jorge Timón
2012-09-25 17:52 ` Gregory Maxwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANEZrP2r6sVC_63xx6U7XLbFkukrFEhq-mGAse3vHJ6nf3Q1cw@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox