Oh snap. Just found a situation where using a for of loop was BLAZINGLY FASTER than using a filter + reduce. Gotta figure out a good way to explain it, because it was just such a huge difference. Like, I'm talking: ~50ms vs ~2 minutes... Or something like that
-
-
Spent the weekend updating the benchmarks for Node 10 and 12 on cloud instances
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Nothing to do with native vs. not. First example he uses a much slower O(n^2) algorithm than the O(n) second example.
-
Correct. Replied before that screenshot was posted. Thanks
Kraj razgovora
Novi razgovor -
-
-
Wow, looked at the benchmarks and there is often a 10x difference *against* native methods! Do you have an explanation as to why native methods are so slow? Are the benchmarks runnable in a browser as well?
- Još 7 drugih odgovora
Novi razgovor -
-
-
I wonder if node12 (and possibly recent releases of libs) changed much in that regard.
-
Yes big time. Mentioned that in other threads. I'm updating the benchmarks for Node 8, 10, 12 LTS all on cloud instances. The problem is it takes nearly all day to run. Will update the repo once they're done
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.