The 166k benchmark is ridiculously snappy. Could you shave off a few more ms by inlining the JSON as a data block?