PERF: pandas read_excel perf optimisations #47376
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WHAT
Attempts on perf optimisations for pandas read_excel
by descending the skiprows (as an integer) to get_sheet_data depending on the engine
openpyxl, xlrd, pyxlsb or odf...
STATUS : Working in progress...
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.BENCHMARKS
BENCH SPECS
OS: Ubuntu 20.04.4 LTS x86_64
Host: 20TH0010FR ThinkPad P1 Gen 3
Kernel: 5.14.0-1038-oem
CPU: Intel i7-10750H (12) @ 5.000GHz
GPU: NVIDIA Quadro T1000 Mobile
GPU: Intel UHD Graphics
Memory: 47849MiB
Python 3.8.6 - [GCC 9.4.0]
BENCH SCRIPT
Fixtures are available here : fixtures
BENCH REPORTS
xls format - - -
xlsx format + + +
xlsb format - - -
ods format - - -
NOTE
Where openpyxl is beeing optimized, other readers's engine are not... but with 'realy low differences'.