)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":36171,"name":"jayaanand borra","display_name":"jayaanand borra","email":"jayaanand.borra@netapp.com","username":"jayaanan","status":"netapp"},"change_message_id":"ae703a14d65627d5b6dd558bb5db8d12e9b69677","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"9b60caff_100c15df","updated":"2026-04-01 04:57:22.000000000","message":"i don\u0027t think 3x improvement. can you please provide concrete example. sha256file is predominantly the sha256s list — an array of 64-character hexadecimal strings\nWith indent\u003d2, each hash entry is represented as     \"\u003c64-char-hash\u003e\",\\n (~72 bytes/hash)\nWithout indent, each hash entry is \"\u003c64-char-hash\u003e\",  (~68 bytes/hash)\nThe structural overhead (indentation + newlines) is minor relative to the hash data itself","commit_id":"f03485daaca1fad229f4a273cdd2e1c5bcbc96d9"},{"author":{"_account_id":34751,"name":"Jasper Ras","email":"jras@hostnet.nl","username":"jrasper"},"change_message_id":"1e2469afdf8f8d99ff537e3a3aa2e8ee7c8ea283","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a3577249_6f2f197c","in_reply_to":"9b60caff_100c15df","updated":"2026-04-01 08:53:20.000000000","message":"Apologies, you are completely right. It appears we\u0027ve had a different configuration running at the time I tested my change which accounted for most the savings, i was a bit too eager here.\n\nAfter isolating it to a small test script it saves only 1277MiB on a file containing 335M hashes (this number of hashes comes from a production case). So while still something, it\u0027s probably negligible in most use cases.","commit_id":"f03485daaca1fad229f4a273cdd2e1c5bcbc96d9"}]}