# Logs of "Mempool in non-optimal ordering after block/additions(s)" **URL:** https://bnoc.xyz/t/logs-of-mempool-in-non-optimal-ordering-after-block-additions-s/125 **Category:** Observations **Created:** [May 12, 2026, 12:33pm UTC](https://bnoc.xyz/t/logs-of-mempool-in-non-optimal-ordering-after-block-additions-s/125 "2026-05-12T12:33:32Z") **Posts on this page:** 5 **Page:** 1
### Author: ![b10c](https://bnoc.xyz/user_avatar/bnoc.xyz/b10c/32/4_2.png) [@b10c](https://bnoc.xyz/u/b10c) #### Post date: [May 12, 2026, 12:33pm UTC](https://bnoc.xyz/t/logs-of-mempool-in-non-optimal-ordering-after-block-additions-s/125/1 "2026-05-12T12:33:32Z")
While chatting with @instagibbs, he mentioned we should not be seeing any `Mempool in non-optimal ordering after X` logs on a node with mempool logging turned on. > > Turns out, while grepping for it, there appear to be a few of these log messages in my logs: ```auto debug.log-20260502-alice.gz:2026-05-02T10:21:57.209033Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260502-alice.gz:2026-05-02T10:21:57.494597Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260502-alice.gz:2026-05-02T10:21:57.543092Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260502-dave.gz:2026-05-02T10:21:57.170824Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260502-dave.gz:2026-05-02T10:21:57.428782Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260502-dave.gz:2026-05-02T10:21:57.481277Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260502-greg.gz:2026-05-02T10:21:58.480026Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260502-greg.gz:2026-05-02T10:21:59.101458Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260502-greg.gz:2026-05-02T10:21:59.246079Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260502-kane.gz:2026-05-02T10:21:57.370745Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260502-kane.gz:2026-05-02T10:21:58.372083Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260502-kane.gz:2026-05-02T10:21:58.387310Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260502-luke.gz:2026-05-02T10:22:00.051254Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260502-luke.gz:2026-05-02T10:22:01.221771Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260502-luke.gz:2026-05-02T10:22:01.869515Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260502-mike.gz:2026-05-02T10:21:58.392768Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260502-mike.gz:2026-05-02T10:21:58.591779Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260502-mike.gz:2026-05-02T10:21:58.620257Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260502-owen.gz:2026-05-02T10:21:56.400585Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260502-owen.gz:2026-05-02T10:21:56.740554Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260502-owen.gz:2026-05-02T10:21:56.927533Z [msghand] [mempool] Mempool in non-optimal ordering after addition(s). debug.log-20260503-alice.gz:2026-05-03T11:07:02.853936Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260503-alice.gz:2026-05-03T22:40:04.199623Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260503-dave.gz:2026-05-03T11:07:03.200111Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260503-dave.gz:2026-05-03T22:40:04.808721Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260503-greg.gz:2026-05-03T11:07:03.733736Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260503-greg.gz:2026-05-03T22:40:07.687305Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260503-kane.gz:2026-05-03T11:07:02.255613Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260503-kane.gz:2026-05-03T22:40:03.207174Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260503-luke.gz:2026-05-03T11:07:07.459751Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260503-luke.gz:2026-05-03T22:40:11.845625Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260503-mike.gz:2026-05-03T11:07:04.036649Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260503-mike.gz:2026-05-03T22:40:05.604810Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260503-owen.gz:2026-05-03T11:07:02.204334Z [msghand] [mempool] Mempool in non-optimal ordering after block. debug.log-20260503-owen.gz:2026-05-03T22:40:03.341977Z [msghand] [mempool] Mempool in non-optimal ordering after block. ``` ---
### Author: ![b10c](https://bnoc.xyz/user_avatar/bnoc.xyz/b10c/32/4_2.png) [@b10c](https://bnoc.xyz/u/b10c) #### Post date: [May 12, 2026, 12:34pm UTC](https://bnoc.xyz/t/logs-of-mempool-in-non-optimal-ordering-after-block-additions-s/125/2 "2026-05-12T12:34:32Z")
I’m now running [GitHub - instagibbs/bitcoin at nonoptimal-cluster-dump · GitHub](https://github.com/instagibbs/bitcoin/tree/nonoptimal-cluster-dump) at [bench: simulate real RBF tail-nip on hard clusters · instagibbs/bitcoin@b36ab29 · GitHub](https://github.com/instagibbs/bitcoin/commit/b36ab29fc76d72785b9815508275dffcbeef4d05) on one of the demo.peer.observer nodes to have some more data to debug this. ---
### Author: ![instagibbs](https://bnoc.xyz/user_avatar/bnoc.xyz/instagibbs/32/34_2.png) [@instagibbs](https://bnoc.xyz/u/instagibbs) #### Post date: [May 12, 2026, 12:37pm UTC](https://bnoc.xyz/t/logs-of-mempool-in-non-optimal-ordering-after-block-additions-s/125/3 "2026-05-12T12:37:34Z")
Copying my comments from IRC: ```auto 14:42 sipa b10c I think what's happening is pretty straight forward: mempool is full of \~25 count linear chain clusters, all roughly the same cfr. a block comes in, skims off a bunch of the cluster prefixes (1 or two tx each), leaving most of hte clusters still with almost a couple dozen. looks like most recent block I measured touched almost 40 such 14:42 clusters, and it exhausts the DoWork budget with \~11 clusters left over. 14:44 obviously it makes good progress each incantation of DoWork ``` So basically I think this could happen even in typical operation. I think seeing how often it happens and how “bad” it is is also helpful for future DoWork re-budgeting efforts that may happen. ---
### Author: ![b10c](https://bnoc.xyz/user_avatar/bnoc.xyz/b10c/32/4_2.png) [@b10c](https://bnoc.xyz/u/b10c) #### Post date: [May 17, 2026, 10:35pm UTC](https://bnoc.xyz/t/logs-of-mempool-in-non-optimal-ordering-after-block-additions-s/125/4 "2026-05-17T22:35:47Z")
I’ve uploaded a few `cluster_dump_1778*.json` files to [BNOC data-share](https://bitcoin-noc.github.io/datashare-website/) into the `2026-05-non-optimal-mempool-dumps` folder. ---
### Author: ![b10c](https://bnoc.xyz/user_avatar/bnoc.xyz/b10c/32/4_2.png) [@b10c](https://bnoc.xyz/u/b10c) #### Post date: [August 5, 2026, 8:21am UTC](https://bnoc.xyz/t/logs-of-mempool-in-non-optimal-ordering-after-block-additions-s/125/5 "2026-08-05T08:21:22Z")
I’ve been running [debug: promote clusters to ACCEPTABLE before non-optimal dump · instagibbs/bitcoin@a2996f6 · GitHub](https://github.com/instagibbs/bitcoin/commit/a2996f6d3d342d94e3a3e7d57b72c418383ea416) since end of may, but haven’t seen any new dumps since then. My understanding is that this means the to-be-dumped clusters aren’t of `ACCEPTABLE` quality. I’ll repurpose the node for something else now, but if this becomes interesting again, let me know.