08:01 < Naphex> https://queue.acm.org/detail.cfm?id=2209336

08:22 < Naphex> "In the problematic situation, packets queued in a network buffer are only dropped if the buffer is full. Having a big and constantly full buffer which causes increased transmission delays and reduced interactivity, especially when looking at two or more simultaneous transmissions over the same channel, is called bufferbloat. Available channel bandwidth can also end up being unused, as some fast

08:22 < Naphex> destinations may not be reached due to buffers clogged with data awaiting delivery to slow destinations, what is caused by contention between simultaneous transmissions competing for some space in an already full buffer." https://en.wikipedia.org/wiki/CoDel

08:22 < Naphex> a fair queue / codel-like scheduling algorithm for the mempool is starting to be needed

08:23 < gmaxwell> this is unrelated to bitcoin---- an entirely different and largely inapplicable area of science which refers deals with adaptive rate control against invisible remote buffers of unknown capacity.

08:23 < Naphex> yes

08:24 < Naphex> but i am looking for some of its properties

08:24 < Naphex> we have a known capacity limit (1MB) and invisible remote buffers of unknown capacity(mempools?)

08:24 < gmaxwell> I haven not seen anything in this space which is applicable (and I was participating in the IETF AQM working group since the first BOF session on it.)

08:25 < gmaxwell> Naphex: mempools are fixed capacity.

08:25 < gmaxwell> (and priority ordered)

08:26 < Naphex> yep but the capacity is a user preference

08:26 < Naphex> although defaults are presented

08:27 < Naphex> yep - and at the moment it displays increased delays and low interactivity

08:27 < gmaxwell> Naphex: what you're doing there is pattern matching words; this doesn't mean that the things are at all related.

08:28 < Naphex> CoDel distinguishes between two "types" of a queue (or rather, the effects produced by a queue): (mempool beeing the queue / confirmed getting pased)

08:28 < Naphex> gmaxwell: i'm trying to explain it better; i am only trying to think of unconfirmed transactions as a queue

08:29 < gmaxwell> You might want to take your brainstorming elsewhere, this channel is for concrete activity around bitcoin core today.

08:30 < Naphex> i'll take your hint

08:31 < gmaxwell> Naphex: you can try #bitcoin-wizards; but without a more coherent view of the applicability I don't know if it will be productive, but someone there might want to discuss it with you.

11:38 < AaronvanW_> is CPFP in use today?

11:53 < aj> eligius uses it i think

11:55 < btcdrak> a patch is coming to Core soon: https://bitcoincore.org/en/meetings/2016/03/03/#child-pays-for-parent-cpfp-mining

12:33 < zibbo> Does anyone have statistics on how many miners implement opt-in rbf logic?

13:48 < GitHub126> [bitcoin] instagibbs closed pull request #7602: [WIP] [RPC] Add call zaptransaction to delete transaction from wallet (master...zaponetx) https://github.com/bitcoin/bitcoin/pull/7602

19:27 < GitHub188> [bitcoin] laanwj closed pull request #7461: Make internal (core) errors show up in the Qt client. (master...propagateAlert) https://github.com/bitcoin/bitcoin/pull/7461