fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
<jistone> fche, I don't recall hearing about this
gmg has quit [Quit: Leaving.]
hpt has joined #systemtap
hpt has quit [Ping timeout: 264 seconds]
orivej has quit [Ping timeout: 240 seconds]
sanoj has joined #systemtap
efiop has quit [Ping timeout: 240 seconds]
sanoj has quit [Ping timeout: 240 seconds]
efiop has joined #systemtap
<serhei> fche, jistone, occurs to me that analysis caching in dyninst may have some relevance to the --remote=kubernetes idea (https://sourceware.org/bugzilla/show_bug.cgi?id=20883)
<serhei> At least, if the caching were easily available, it would make sense to do the analyzing separately from the instrumenting
<serhei> Don't know if it will translate into helpful performance improvements, or if dyninsting a containerized program is an easy proposition atm
scox has quit [Ping timeout: 240 seconds]
scox has joined #systemtap
scox has quit [Ping timeout: 255 seconds]
scox has joined #systemtap
sona has joined #systemtap
orivej has joined #systemtap
<fche> serhei, that'd be even harder - to do the analysis remotely/centrally
hpt has joined #systemtap
hpt has quit [Read error: Connection reset by peer]
sona has quit [Ping timeout: 268 seconds]
hkshaw has joined #systemtap
hkshaw has quit [Ping timeout: 268 seconds]
sona has joined #systemtap
sona has quit [Ping timeout: 240 seconds]
sona has joined #systemtap
Humble has quit [Ping timeout: 260 seconds]
Humble has joined #systemtap
Humble has quit [Ping timeout: 255 seconds]
sona has quit [Ping timeout: 255 seconds]