14:28:52 #startmeeting metrics team 14:28:52 Meeting started Thu Aug 9 14:28:52 2018 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:28:52 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:29:21 I wonder what to put on the agenda today.. 14:29:50 okay, let's go with your topic: 14:29:55 Onionoo questions (irl) 14:30:06 what questions are that? 14:30:21 so basically it's some questions about the architecture 14:30:30 ok. 14:30:42 i noticed that i wasn't able to sync the out/state directories locally in the time between runs 14:30:53 :( 14:30:57 as i'd already done a copy, i was expecting to just get diffs for currently running relays 14:31:09 but it looks like onionoo writes out every file every time 14:31:19 i wondered why it did this, if we expected this to be happening? 14:31:30 I don't think it writes every file. 14:31:36 it probably writes a lot of the details files. 14:31:49 the details files did take the longest to copy 14:32:02 yes, that might be the case. 14:32:05 but for each of the document types it was a lot more than just the number of running relays+bridges 14:32:42 i guess the question is, for each run how many files do we expect to be touched? 14:32:59 we do have statistics how many are being touched. 14:33:31 ah cool, i didn't think of that (: 14:33:36 so, we can probably optimize this. 14:33:47 what's the goal? easier backups? or also faster update runs? 14:33:55 or something else? 14:34:06 both and also easier spin up of testing environments 14:34:25 essentially what i'm doing is a backup and a restore to another machine 14:34:55 i think it's likely that we don't currently have any consistent backups, that is they are all changed during the backup 14:35:28 that might be the case, yes. 14:35:46 what we could do: read a file before writing it and only write it if it's different. 14:36:15 yes, this would be great 14:36:32 irl-abdn: can you please look at the email and ticket on the removal of the ooniprobe debian packages on deb.tpo (sorry to bug you here, but this is pretty urgent)? 14:36:33 to speed things up i was only comparing timestamps and filesizes, not performing diffs and checksums over ssh 14:36:33 maybe modified to: check the file size, and if it's different, write. if it's the same, check more thoroughly. 14:36:48 irl-abdn: feel free to do hellais' thing first. 14:37:55 hellais: aaah! i didn't realise it was still an advertised installation method 14:38:23 hellais: i am not currently with any keys so won't be able to fix until later today 14:38:33 hellais: i will make it priority when i am back with keys though 14:38:49 karsten: yes, this seems sensible 14:39:06 anything we can do in onionoo when it's close to the data is better for backup tools that are maybe working over the network and would be slower 14:39:08 irl-abdn: want to create a ticket and look into this? or should I start looking? 14:39:36 karsten: it is up to you, if you'd like me to do it then i'll have to create the ticket later 14:39:40 as i can't log in to trac right now 14:39:56 we can always make todo list on the pad 14:40:12 added to the pad for now. 14:40:38 do you have more questions regarding onionoo? 14:40:57 one other 14:41:02 sure! 14:41:12 is the out/ directory able to be entirely reconstructed from the status/ directory? 14:41:18 heh. 14:41:27 hopefully. 14:41:27 i remember a ticket about the out/ directory writing being deterministic 14:41:33 i don't remember if it was completed 14:41:38 yes, but I'm not 100% certain that it's the case. 14:41:43 I'd say, give it a try. 14:41:48 maybe this is a shortcut that we can use to speed up backups 14:41:59 it won't get us all the way there but it does halve the time 14:42:10 so, it should be. 14:42:40 maybe we should add some test cases for this? 14:42:56 we don't really have tests on that level. 14:43:15 irl-abdn: ok thank you very much. 14:43:39 so, for now, I'd say let's try it out. and if it's not the case, let's fix that. 14:43:49 ok cool 14:44:02 i did eventually get a copy of the status and out directory this morning 14:44:06 so i have something to play with 14:44:17 that's good! 14:44:33 by the way, I also broke an onionoo instance when making backups the other day.. 14:44:52 I needed a copy of the out/ directory to test the local tool that fixes broken json files. 14:45:15 right 14:45:29 i wanted to test the rewriting and the upgrade all together 14:45:48 which i can now do, it was just a bit of a pain to get to being ready for it 14:45:52 what do you think, when can we deploy the fixes? 14:45:58 i didn't get to testing it yet 14:46:02 only being ready to test it 14:46:09 sure. just to have an estimate. 14:46:17 oh, probably monday? 14:46:22 ok. 14:46:54 cool! 14:46:59 this is all my questions 14:47:27 did you have other topics? 14:47:30 okay. I don't really have more topics. most things are in trac tickets already. 14:47:58 ok cool 14:47:58 in which case let's go async again, if that's okay for you? 14:48:09 yep, sounds good (: 14:48:20 great. have a nice day! bye. :) 14:48:32 #endmeeting