You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the interest of analyzing the results, it would interesting to measure the time spent on update operations. E.g. for Umbra this would entail measuring the time spent on 22 operations: 14 inserts and 8 deletes:
It's rather impractical to save the parameters of the entities to the timings file (it would grow massive with billions of operations on SF10,000), so a good schema for storing the results in timings.csv would be:
For the interest of analyzing the results, it would interesting to measure the time spent on update operations. E.g. for Umbra this would entail measuring the time spent on 22 operations: 14 inserts and 8 deletes:
It's rather impractical to save the parameters of the entities to the timings file (it would grow massive with billions of operations on SF10,000), so a good schema for storing the results in
timings.csv
would be:This would allow to see what the decomposition of the writes is (inserts, deletes, precomputations).
The text was updated successfully, but these errors were encountered: