alteryx / alteryx/evalml

Understand our data copying

Aperta
#3,296 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
performance spike tech debt
Lingua principale
Python
Stelle
850
Fork
96
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

In @bchen1116 's recent analysis of our ensembling algorithm, it's come to light that we spend a lot of time copying data. I've noticed throughout the code a lot of copying of dataframes and think we should understand all these copies and whether they're necessary or just impediments to performance.

Acceptance criteria for this issue is a benchmarking and profiling of our unit test suite and visualization with snakeviz. @bchen1116 if you could also link or copy/paste your results you showed earlier today, that would be helpful to highlight the problem.

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.