Programming

17377 readers

259 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

how do you fix an issue you can't reproduce? a case study (www.youtube.com)

submitted 4 months ago by LGUG2Z@lemmy.world to c/programming@programming.dev

0 comments fedilink hide all child comments

I'm sure most of us have had to deal with issues reported by end users that we ourselves aren't able to reproduce

This video is an extended case study going through my thought process as I tried to track down and fix a mysterious performance regression which impacted a small subset of end users

I look at the impact of acquiring mutex locks across different threads, identifying hot paths by attaching to running processes, using state snapshot comparisons to avoid triggering hot paths unnecessarily, the memory implications of bounded vs unbounded channels, and much more

no comments (yet)

sorted by: hot top controversial new old

there doesn't seem to be anything here