finer timing in ManifoldCAD.org

[elalish]

I've been playing around with timing our mesh smoothing SDF vs increasing SDF resolution, but the timings were giving me odd results: see this ManifoldCAD example. Turns out most of the time was being spent in file export, not the actual Manifold library. So here I've split the timing into two parts: Manifold time and export time.

However, during the process I found that GLB export is next to instant - the real time killer is 3MF export, particularly the zip. I'm thinking now it would be better to do the 3MF export on save rather than on run. I wonder if we can just pass the whole to3mf JSON object out of the worker? Makes the API a bit less clean, but...

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.87%. Comparing base (a13ceab) to head (346a0a5).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1099   +/-   ##
=======================================
  Coverage   91.87%   91.87%           
=======================================
  Files          30       30           
  Lines        5883     5883           
=======================================
  Hits         5405     5405           
  Misses        478      478           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[pca006132]

Sorry, but I really want to make a meme for this:

[elalish]

I guess I'll go ahead an merge this for now, though I think now the better course will be to revert this, have the worker only generate a GLB, then have the Save3MF button convert the GLB to a 3MF. This'll simplify our worker API too, which will make it nicer to put out as its own npm package. But that'll take longer, so it'll have to wait.