Preferences

tanelpoder
Joined 4,651 karma
A long-time computer performance nerd, creator of 0x.tools

blog: tanelpoder.com


  1. From the post:

    "This improvement comes from a redesigned Windows storage stack that no longer treats all storage devices as SCSI devices"

    And:

    "Direct, multi-queue access to NVMe devices means you can finally reach the true limits of your hardware."

  2. This also leaves more power & thermal allowance for the IO Hub on the CPU chip and I guess the CPU is cheaper too.

    If your workload is mostly about DMAing large chunks of data around between devices and you still want to examine the chunk/packet headers (but not touch all payload) on the CPU, this could be a good choice. You should have the full PCIe/DRAM bandwidth if all CCDs are active.

    Edit: Worth noting that a DMA between PCIe and RAM still goes through the IO Hub (Uncore on Intel) inside the CPU.

  3. At an old startup attempt we once created a nested hierarchy metrics visualization chart that I later ended up calling Bookshelf Charts, as some of the boxes filled with with smaller boxes looked like a bookshelf (if you tilted your head 90 degrees). Something between FlameGraphs and Treemaps. We also picked “random” colors for aesthetics, but it was interactive enough so you could choose a heat map color for the plotted boxes (where red == bad).

    The source code got lost ages ago, but here are some screenshots of bookshelf graphs applied to SQL plan node level execution metrics:

    https://tanelpoder.com/posts/sql-plan-flamegraph-loop-row-co...

This user hasn’t submitted anything.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal