~/talk

Energy Implications of Your Go code

on YouTube 32m
Talkat GopherCon UK 2019 · 2019-08-21..08-23· [go, web-performance]

speaker

name:Mahdi Jelodari
links:none on file

resources

video:https://youtu.be/4f_Xy24rUYo
slides:none on file

summary

Edge devices spend ~65% of energy on data movement so experiments use Intel RAPL energy counters and Go tooling (go test bench, runtime/trace) to compare three PageRank implementations: a dense matrix version, a goroutine-per-vertex Pregel variant, and a sequential stream implementation. Measurements show the sequential stream runs faster and uses less energy on sparse graphs, Pregel causes heavy cross‑core communication and heap churn, and stack locality plus reduced data movement cuts power.

AI-written summary · about

chapters (9)

  1. 0:00Introduction
  2. 3:36Performance vs energy in Go
  3. 7:13Data movement costs
  4. 10:57Graph processing with Pregel
  5. 15:30Benchmarking energy in Go
  6. 21:04Power tools and traces
  7. 24:40Energy-saving Go guidelines
  8. 28:49Scheduling for energy
  9. 30:40Go in robotics and Python

related talks

~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.