Øyvind Harboe

> Yeah I think bazel is pretty agnostic to storage. I think the only way you get compression is with that flag I mentioned previously. Nice find! I will experiment...

> OR already has support for GZip on LEF, DEF, and SPEF. I don't think it would be too much to ask for ODB as well. Sure, but not relevant...

> Ah I did not read the edited original post. I mean, I don't really know what to do there, other than turning up the compression effort on GZip which...

> On Jpeg sky130 the routed odb goes from 360Mb to 180MB. ZSTD compression is about 37MB, Nice! What was the difference in conmpressed size?

> 1-2MB I see... Not to be a party pooper, but then it looks like it is better to just leave this to generic compression than to add make OpenROAD...

> Yeah I think adding a streaming zstd encoder by default makes the most sense. It's already in boost so it'll be an easy add. It's pretty fast 500MB+ encode...

> Maybe there could be a compressed structure for arrays of fill cells? Something that just stores {x_origin, y_origin, x_pitch, y_pitch, x_count, y_count} plus some way of incrementing the instance...

Just as a datapoint, bsdiff is not practical, took hours. ``` $ bsdiff 3_place.odb 4_cts.odb patchfile $ zip xx patchfile updating: patchfile (deflated 0%) $ unzip -lv xx.zip Archive: xx.zip...

@maliberty An idea for macro placement specifically: write out a placemen.tcl, which fully describes the result of the .odb file from macro placement and read it back in in the...

@maliberty Close? I think we covered the difference in significance between size of compressed and uncompressed .odb files and that this is now well understood. Uncompressed size helps runtime, compressed...