-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize sort_by_key (SortFaces/SortVerts) #494
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #494 +/- ##
=======================================
Coverage 90.23% 90.23%
=======================================
Files 35 35
Lines 4391 4391
=======================================
Hits 3962 3962
Misses 429 429
☔ View full report in Codecov by Sentry. |
interesting, I guess these recent optimizations means that sort_by_key and sort using zip iterators are very slow? I originally thought that the performance should be fine. |
Nah sort_by_key is fine. Actually you could use The only thing that matters is the size of the object to move (both keys or values), here by sorting boxes we are moving big objects an unnecessary amount of time. |
Remap boxes separately
For the build error, I think we hit the #460. The safer way I can now think of is to use clang. Try to add the following commit: diff --git a/flake.nix b/flake.nix
index 04ffc90..4c37ab3 100644
--- a/flake.nix
+++ b/flake.nix
@@ -16,7 +16,7 @@
, doCheck ? true
, build-tools ? [ ]
, ...
- }: pkgs.stdenv.mkDerivation {
+ }: pkgs.llvmPackages_15.stdenv.mkDerivation {
inherit doCheck;
pname =
if cuda-support then
it seems that this is no longer relevant?
Wondering what benchmark are you using? Wonder if you can share them to the unit tests? This can help us track performance later. |
* Optimize sort_by_key (SortFaces/SortVerts) Remap boxes separately * Fix build validation
Remap boxes separately
MacOS M1/TBB: 1485ms -> 1385ms