4 ms·
Twitter's Ruby on Rails problem that the parent mentions - @26:30 https://youtu.be/LjFM8vw3pbU?t=1591 https://youtu.be/LjFM8vw3pbU?t=1591
by snvsn 5y ago
Twitter's Ruby on Rails problem that the parent mentions - @26:30 https://youtu.be/LjFM8vw3pbU?t=1591 https://youtu.be/LjFM8vw3pbU?t=1591
- josephg 5y agoThats the one - thankyou! Its interesting that google doesn't index the transcript of youtube talks. Great detail I'd forgotten: At the time twitter took 460ms of compute to process each request. Almost all the CPU time was in bcopy, constructing the big string backtraces for exceptions (that were then being immediately discarded).