16:58:50 #startmeeting Network team meeting, 21st June 2022 16:58:50 Meeting started Tue Jun 21 16:58:50 2022 UTC. The chair is ahf. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:58:50 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:58:54 yo yo yo 16:59:05 hiya! 16:59:09 Afternoon. 16:59:13 welcome to this meeting that will feel like it's still monday the 13th since all days in last week seemed a bit like it was monday 16:59:16 our pad is at https://pad.riseup.net/p/tor-netteam-2022.1-keep 16:59:22 o/ 16:59:34 o/ 16:59:56 o/ 16:59:58 o/ 17:00:00 okay, how are folks doing with their boards: https://gitlab.torproject.org/groups/tpo/core/-/boards ? 17:00:24 * eta is okay 17:00:39 doing okay here too. 17:00:56 mikeperry: if you could get me some updated RTT test vectors that would be very appreciated, btw 17:01:08 do take a moment to notice the much smaller number of tickets open thanks to, especially, nickm's epic triage round thursday+friday 17:01:15 though I think the next thing I'm going to tackle is probably the ntor handshake 17:01:19 a bit stalled here while this DoS is ongoing and I keep trying to find ways to stop it 17:01:27 ahf: nickm+dgoulet 's epic triage :) 17:01:42 eta: Could trouble you for the rereview on the channel MR ? 17:01:53 eta: yeah, sorry, I got paralyzed by DoS and stuff; also was a bit wary of updating the spec publicly before release packages were out 17:02:02 * eta nods 17:02:03 but I can do it this week 17:02:16 wfm! I don't think I should be that blocked on it for a while 17:02:30 mikeperry: You need to ask me for something you're blocked on, now, I think ? To make it a full circle (triangle) 17:02:45 nickm: ya! 17:03:26 ok, i don't see anything off 17:03:41 dgoulet: on releases, i don't think we have anything here, right? nice work with the emergency release that happened 17:03:42 nickm: I haven't said this yes, so: thanks for digging through tickets! I hope you enjoyed it more than I would have! 17:03:51 yeah security release on friday... 17:03:55 Diziet: I guess rust prevents deadlocks so we need to invent them at the team level? keep things spicey! ;) 17:04:01 Diziet: I love that kind of thing 17:04:03 got a bit messy at the end with that CVE waiting time but we got it.... 17:04:04 that is about it 17:04:13 nickm: I love that I have you on our team, then :-) 17:04:37 mikeperry: (Also Rust totally doesn't prevent deadlocks, sadly...) 17:04:37 dgoulet: very nice - thank you! 17:04:43 it looks like we don't have anything bad incoming 17:04:45 "That's what makes horse races" 17:04:46 Diziet: I'll push it onto my stack 17:04:52 eta: Ta. 17:05:01 I've now forgotten whether I was okay with tolerating the ChannelsConfigUpdates thing 17:05:11 You said you'd live with it, iirc. 17:05:18 that sounds like something I'd say :p 17:05:25 lol 17:05:29 https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/586#note_2814258 last para 17:05:47 I was paraphrasing, in fact. I think it may be the kind of thing that I would say. 17:05:57 I'll go check 17:06:57 That's what I took as a grudging OK. If you still feel it's a premature optimisation and want it reworked I think we'll have to have a conversation about that but not here. 17:07:22 Diziet: I still think it's a premature optimisation, actually 17:07:47 (looking back at the scrollback, I think that was where I intended to leave things before the passport office got in the way :p) 17:08:20 though, sure, we can chat about that — I'm receptive to the idea that you might not want to rework it any more if you've already done a fair amount of that :p 17:08:34 Let's take that to #tor-dev after this meeting? 17:08:39 wfm 17:08:51 ok! 17:09:12 we have two topics 17:09:20 [2022-06-21] [nickm] Anything to do to prep for hackweek next week? 17:09:35 i think the important thing is that people find something they want to work on here 8) 17:10:16 how does the hackweek work? 17:10:24 oof, next week. that snuck up on me :) 17:10:29 (are we dropping everything to focus on the hackweek tasks?) 17:10:33 I see an email from 26th of May which err I seem to have spaced. 17:10:43 ya 17:10:47 also no meetings 17:10:55 sweet 17:10:55 eta: you can present a proposal or join one of the proposals already presented 17:10:59 is a good idea to try to team up also with people outside of just the netteam 17:11:09 https://hackweek.onionize.space/hackweek/schedule/#0 (ignore the 17:11:09 "time/date") 17:11:51 The CFP deadline https://hackweek.onionize.space/hackweek/cfp is ... quite relaxed. 17:11:56 perhaps I'll go help richard with gosling :p 17:12:57 ahf: I'd like to pick your brain after the meeting about whether any of the ideas I suggested are things I should offer to do 17:13:13 ok, sounds like people are now *aware* of it at least, so spend some time this week looking at options or create options here 8) 17:13:28 nickm: cool! i think i can give feedback but in the end it is also what you would like to do 17:13:30 Is it possible to see the other proposals or is that what "Schedule" is ? 17:13:39 emmapeel: ^^ 17:13:45 (I think the schedule is indeed a list of other proposals, aiui?) 17:13:48 I don't know if the schedule == 100% of the other proposals or not :) 17:13:57 ah 17:14:23 yes, the schedule is a list of other proposals AFAIK 17:14:33 maybe there are more proposals, ggus may know more about this 17:14:36 i think people can propose multiple things, but they end up only working on one 17:14:57 please ignore the date/time 17:15:03 yes, rhatto was wondering what to do with his 2 proposals as well 17:15:22 nice 17:15:27 ok, i am gonna move to next item: 17:15:31 [2022-06-21] [nickm] Next arti release date? (This friday or next friday?) 17:15:31 That list of proposals is ... quite short given the number of people, I think ? 17:15:43 From which, can I infer that everyone else is as late as me ? 17:15:44 Diziet: i think people are, like us, a bit "oh already next week" right now 17:15:46 but as we can stop work in sponsor deliverables, and meetings, we also have more time 17:15:52 ahf: lol right 17:16:07 (sorry, lag) 17:16:40 nickm: i would say this friday given the above discussion? 17:17:16 works for me; it'll come out earlier than it would have otherwise, but it will encourage us to pay attention to the hackweek instead 17:17:38 arti releases don't seem to generate fallout that means we have to put out fires. (I don't think we have that many users yet...) 17:18:06 i think everybody should clear their minds for hackweek so they can dive into something new without having things in the back of their heads 17:18:18 ... i know this will likely be impossible with the DoS ongoing too, but .. :-/ 17:18:53 anything else we need to discuss before we move to s61? 17:19:21 all good here :) 17:19:42 mikeperry: wanna dive into s61 ? 17:19:45 ok 17:20:21 so hiro and i have been looking at different guard and CBT params: https://gitlab.torproject.org/tpo/network-health/analysis/-/issues/37 17:20:49 we set up new onionperf 7a instances with 2 guards + 70% cbt cutoff, and 3 guards with 66% CBT cutoff 17:21:11 the theory being that more guards plus lower CBT could avoid relays overloaded due to dos 17:21:39 3 guards + 66% CBT seems to result in about a 2X throughput boost 17:21:54 2 guards + 70% CBT is maybe 1.25-1.5X.. but it is hard to see 17:22:23 hiro: I think we're gonna need to get the tornetools workflow going, as per https://gitlab.torproject.org/jnewsome/sponsor-61-sims/-/issues/17 17:23:02 because the days of good vs bad perf from this DoS are all over the place 17:24:32 if we get all that filtering done, we can cross-reference sbws and see how much changing Guard+Fast cutoffs helps. 17:25:32 we could change the guard and CBT params with consensus param update right now, and this would help people, but perhaps not as much as actually changing those cutoffs 17:25:49 though changing the flag cutoffs requires a consensus update.. 17:26:37 hiro: so I will likely be pinging you trying to get some tornettools workflow soon 17:27:28 juga was also looking at sbws votes in https://gitlab.torproject.org/tpo/network-health/analysis/-/issues/40 17:27:53 it looks like two of our bw auths have a throughput bottleneck of around 25Mbit :/ 17:28:32 I believe sbws is the main thing that is making the DoS not be miserable, all of the time.. but with only one guard, some users are probably still getting unlucky 17:29:42 we also had the TROVE, of course. we still see no evidence of active exploitation AFIACT 17:29:48 farahavar can do around 35Mbit at least 17:29:49 but yeah 17:29:59 we would see this evidence in https://gitlab.torproject.org/tpo/network-health/analysis/-/issues/38 17:30:33 as well as relay logs 17:31:25 in general the DoS is really fucking up my world. it looks like sbws upgrading to CC was a major missing piece of our bad perf wrt not matching what shadow predicted 17:31:28 *faravahar actually 17:31:33 but with the DoS, it is very hard to tell now 17:32:35 need to call a timeout with the DoSers so we can get some measurements... 17:33:41 do we have a new Exit upgrade rate datapolint for 0.4.7? 17:34:11 jnewsome: :s 17:34:49 mikeperry: it's not making any progress anymore 17:35:01 what is the percentage? 17:35:31 hiro: We can also filter out non-upgraded Exits for https://gitlab.torproject.org/jnewsome/sponsor-61-sims/-/issues/17 17:35:45 1297: 0.4.7 [81.28 %] [84.34 %] (MAJOR) 17:36:00 the first is consensus weight 17:36:06 the other is adv bw 17:36:20 that's exits fwiw 17:36:29 yeah ok 17:36:31 thanks 17:36:36 whole network is 17:36:38 4210: 0.4.7 [64.99 %] [63.05 %] (MAJOR) 17:37:55 ok 17:38:41 so yeah, major action items are https://gitlab.torproject.org/jnewsome/sponsor-61-sims/-/issues/17, and trying to work with bastet and Farahavar bwauths to figureout if they can improve their bottleneck 17:39:08 and I will update the spec and test vectors for the TROVE 17:39:20 mikeperry: i'm still working on simulating link sharing as well 17:39:50 mikeperry: should i wait looking closer into: https://gitlab.torproject.org/tpo/network-health/analysis/-/issues/38 17:39:52 ? 17:40:14 right now i am wary that this would be a timesink not giving us the data anyway we want 17:40:25 GeKo: I think looking at the sbws votes for those outliers may be useful, but yeah, it may need several days of datapoints 17:40:37 i could deprioritize it if you no longer think it's likely to be a major factor, though at this point might as well try to finish the implementation while it's fresh in my mind. https://gitlab.torproject.org/jnewsome/sponsor-61-sims/-/issues/16#note_2811688 17:40:44 none of them get the overload flag? 17:41:09 i could check that but i doubt it 17:41:31 given that only one op*a instance has issues with any of them 17:41:46 jnewsome: yeah, worth finishing.. but ideally we would compare against a post-sbws upgrade time period.. but all of those are riddled with DoS, so it is hard to say if we're making it closer to reality now, or just closer to the DoS state 17:41:56 so, it seems there should be a different reason for almost any of them showing up on the outliers than general overload 17:43:35 dgoulet is noticing that the DoS appears to be moving around.. so it may be emphermeral wrt this.. but it might also be worth trying it later in the week once we have several days of data to look through 17:44:07 okay. i'll look a bit more then 17:46:23 I think that is it for me. any questions? 17:46:54 * ahf is good 17:47:31 me too 17:47:59 let's call it 17:48:02 thanks folks! 17:48:06 peace all! 17:48:06 #endmeeting