alteryx / alteryx/evalml

Understand our data copying

Open
#3,296 0 comments 0 reactions 0 assignees View on GitHub
performance spike tech debt
Dominant language
Python
Stars
850
Forks
96
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.