core-lightning/gossipd/gossip_store.csv

# gossip_store messages: messages persisted in the gossip_store
# We store raw messages here, so these numbers must not overlap with
# 256/257/258 or gossipd_local_add_channel (3503)

# This always follows the channel_announce.
msgtype,gossip_store_channel_amount,4101
msgdata,gossip_store_channel_amount,satoshis,amount_sat,

msgtype,gossip_store_private_update,4102
msgdata,gossip_store_private_update,len,u16,
msgdata,gossip_store_private_update,update,u8,len
gossipd: use a separate CSV file for the gossip_store types. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-04-11 01:03:36 +02:00			`# gossip_store messages: messages persisted in the gossip_store`
gossip_store: change format so we store raw messages. Save some overhead, plus gets us ready for giving subdaemons direct store access. This is the first time we upgrade the gossip_store, rather than just discarding. The downside is that we need to add an extra message after each channel_announcement, containing the channel capacity. After: store_load_msec:28337-30288(28975+/-7.4e+02) vsz_kb:582304-582316(582306+/-4.8) store_rewrite_sec:11.240000-11.800000(11.55+/-0.21) listnodes_sec:1.800000-1.880000(1.84+/-0.028) listchannels_sec:22.690000-26.260000(23.878+/-1.3) routing_sec:2.280000-9.570000(6.842+/-2.8) peer_write_all_sec:48.160000-51.480000(49.608+/-1.1) Differences: -vsz_kb:582320 +vsz_kb:582316 -listnodes_sec:2.100000-2.170000(2.118+/-0.026) +listnodes_sec:1.800000-1.880000(1.84+/-0.028) -peer_write_all_sec:51.600000-52.550000(52.188+/-0.34) +peer_write_all_sec:48.160000-51.480000(49.608+/-1.1) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2019-05-04 07:53:12 +02:00			`# We store raw messages here, so these numbers must not overlap with`
			`# 256/257/258 or gossipd_local_add_channel (3503)`
gossipd: use a separate CSV file for the gossip_store types. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-04-11 01:03:36 +02:00
gossip_store: change format so we store raw messages. Save some overhead, plus gets us ready for giving subdaemons direct store access. This is the first time we upgrade the gossip_store, rather than just discarding. The downside is that we need to add an extra message after each channel_announcement, containing the channel capacity. After: store_load_msec:28337-30288(28975+/-7.4e+02) vsz_kb:582304-582316(582306+/-4.8) store_rewrite_sec:11.240000-11.800000(11.55+/-0.21) listnodes_sec:1.800000-1.880000(1.84+/-0.028) listchannels_sec:22.690000-26.260000(23.878+/-1.3) routing_sec:2.280000-9.570000(6.842+/-2.8) peer_write_all_sec:48.160000-51.480000(49.608+/-1.1) Differences: -vsz_kb:582320 +vsz_kb:582316 -listnodes_sec:2.100000-2.170000(2.118+/-0.026) +listnodes_sec:1.800000-1.880000(1.84+/-0.028) -peer_write_all_sec:51.600000-52.550000(52.188+/-0.34) +peer_write_all_sec:48.160000-51.480000(49.608+/-1.1) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2019-05-04 07:53:12 +02:00			`# This always follows the channel_announce.`
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-24 00:51:11 +02:00			`msgtype,gossip_store_channel_amount,4101`
			`msgdata,gossip_store_channel_amount,satoshis,amount_sat,`
gossipd: use a separate CSV file for the gossip_store types. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-04-11 01:03:36 +02:00
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-24 00:51:11 +02:00			`msgtype,gossip_store_private_update,4102`
			`msgdata,gossip_store_private_update,len,u16,`
			`msgdata,gossip_store_private_update,update,u8,len`