Skip to content

Write Bandwidth Project Meeting Notes

Jump to bottom
Alex Miller edited this page Mar 18, 2020 · 11 revisions

3/18/2020

  • Pipelining
    • With Chrome Tracing, we now have some tools we can use to investigate commit pipelining.
    • How do we identify issues? What do we think could be issues? What tests should we be running to find issues?
    • Setting \xff\x02/timeKeeper/disable will disable timekeeper, which is the every 10s debug transaction.
    • Trevor is doing work in this area also. Will invite him to future meetings.
      • Investigating instances where more time being spent in proxy than waiting for tlog fsync.
    • Resolvers cannot just be turned off for conflict-free workloads due to their involvement in \xff
  • Other improvements
    • Rusty's event loop 2.0?

To do for next week:

  • The suspicion is there there should be one proxy that is slower than the others.
  • Confirm from the trace that resolvers are waiting on pipelining, and preferably that one proxy is indeed slower
  • Look into or add proxy batching to traces
  • If there is indeed one slow proxy, then work on single proxy CPU usage and profiling
  • Sync with Trevor on his current state of proxy profiling

Clone this wiki locally