00:22:15 <abberant[m]> <DataHoarder> "although if you restart it might..." <- yeah, this is beyond that tho
00:22:22 <abberant[m]> 🤷
16:21:07 <hyc> sech1: running the api branch off master, getting a bunch of err msgs. pasted in -dev
16:25:19 <sech1> where does it come from? I don't see how it could be related to my changes
17:24:16 <hyc> no idea
17:24:27 <hyc> load_binary seems a strange call to be happening
18:17:44 <mightysnowman[m]> what how people getting 11,3kh/s with 7 3800x meanwhile max I'm getting is 7,5k
18:18:16 <mightysnowman[m]> is ram speed a really big factor?
18:18:21 <DataHoarder> yes, and channels
18:18:28 <mightysnowman[m]> my ram at 2400mhz
18:19:10 <DataHoarder> probably bump that, "Enforce POR" option on server stuff for me is disabled :)
18:19:21 <DataHoarder> no need to OC specifically, but you can rise that
18:19:33 <DataHoarder> then the classic, hugepages, msr, etc.
18:21:28 <mightysnowman[m]> and CL17-17-17-39
18:22:00 <DataHoarder> I never went towards optimizing that much
18:22:10 <DataHoarder> already running ECC here with registered/buffered RAM
18:22:54 <mightysnowman[m]> my mobo supports ram tweaking but for that ram I dont seem to be able to change anything
18:23:18 <DataHoarder> there should be an option to remove the "baseline" DDR4 limit, on the original spec
18:23:21 <DataHoarder> even on servers
18:23:22 <hyc> registered ECC is already going to be higher latency, nothing you can do about that
18:23:38 <DataHoarder> (yeah, I know, not trying to fix my setup)
18:24:49 <wfaressuissia> DataHoarder, do you have deep knowledge in networking ?
18:26:41 <DataHoarder> Perhaps
18:30:57 <wfaressuissia> What packets will receive DDoS target if there are two attackers with equal outgoing bandwidth and their cumulative bandwidth is much larger than incoming bandwidth of target ?
18:31:18 <wfaressuissia> Would it receive uniformly chosen packets with 50%/50% probability from both attackers ?
18:31:35 <wfaressuissia> or it would be complete disconnect without 0 incoming packets 
18:31:45 <wfaressuissia> s/without/with/
18:36:50 <DataHoarder> that is indeed deep, and I guess we are assuming paths taken by DDoS end up using same peerings on average towards final path, and previous paths don't die to it, let's say all reach
18:37:50 <DataHoarder> second is probably a no-no as "disconnect" doesn't just happen, packet loss due to lack of memory on what passes packets on to the final target
18:38:02 <DataHoarder> (that needs to be a programmed action)
18:38:43 <DataHoarder> can't say about 50%/50%, that gets too deep and from having written some firmware for 100G cards as hobby it still doesn't give me answers
18:38:49 <DataHoarder> don't know enough there
18:39:51 <DataHoarder> do you have an answer wfaressuissia, given it is DDoS I would say packets are random from both sides... so there is no single source to favor
18:40:41 <DataHoarder> I just know some of the code I saw preferred certain sources depending which packets had gotten to it slightly
18:40:56 <DataHoarder> anyhow, this is kind offtopic for this channel
22:09:58 <selsta> 18:21 <@hyc> sech1: running the api branch off master, getting a bunch of err msgs. pasted in -dev <-- it's unrelated to any PRs
22:10:23 <selsta> it's just someone changing source code to spam nodes, it's harmless apart from spam
22:12:31 <selsta> log spam*