***: ziyourenxiang has joined #arpnetworks
qbit[m]1 has joined #arpnetworks
up_the_irons2 has joined #arpnetworks
d4c4 has joined #arpnetworks
toddf_ has joined #arpnetworks
ChanServ sets mode: +o toddf_
DaCa has quit IRC (Ping timeout: 276 seconds)
qbit[m] has quit IRC (Ping timeout: 276 seconds)
up_the_irons has quit IRC (Ping timeout: 276 seconds)
karstensrage has quit IRC (Ping timeout: 276 seconds)
toddf has quit IRC (Ping timeout: 276 seconds)
MeltedLux has quit IRC (Ping timeout: 276 seconds)
karstensrage has joined #arpnetworks
karstensrage is now known as Guest74281
MeltedLux has joined #arpnetworks
qbit[m]1 has quit IRC (Ping timeout: 248 seconds)
qbit[m]1 has joined #arpnetworks nathani: up_the_irons : Happy Invoice Day! layer8problem: up_the_irons: thanks. I'm re-reading the "introducing..." article. It sounds as though each of the bare metal resources is dedicated for the "thunder" vps running on top of it. Is this a matter of just saying how many each is allowed to use, or do you use techniques like process sets, or cpu affinity, etc to keep it to the same cores? I'm thinking through things like having cache lines blown out if which physical cores are ha
ndling execution can change ***: Guest74281 is now known as karstensrage
karstensrage is now known as Guest68163
Guest68163 is now known as karstensrage
karstensrage has quit IRC (Changing host)
karstensrage has joined #arpnetworks
ziyourenxiang has quit IRC (Quit: Leaving) up_the_irons2: mhoran: we'll be migrating VMs off kvr02 actually, soon... mhoran: I'll finally get virtio! :D mercutio: virtio doesn't help openbsd that much mhoran: Good thing I'm running freebsd!
I thought it'd help some io latency I was seeing a while back but I don't remember if it helped mercutio: ah cool
yeah virtio helps more with freebsd
it mostly helps with writes on freebsd iirc
and mostly helps with reads on openbsd mjp2: how is spectre/meltdown handled? ***: layer8problem has quit IRC (Read error: Connection reset by peer)
layer8problem has joined #arpnetworks