Skip to content

IO: memory_map kw in read_csv #7477

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

Closed
jreback opened this issue Jun 16, 2014 · 2 comments
Closed

IO: memory_map kw in read_csv #7477

jreback opened this issue Jun 16, 2014 · 2 comments
Labels
Docs IO CSV read_csv, to_csv IO Data IO issues that don't fit into a more specific label

Comments

@jreback
Copy link
Contributor

jreback commented Jun 16, 2014

not sure of the purpose of memory_map (e.g. whether its needed anymore or not). might be an older option. If it IS current, then needs to be documented.

@jreback jreback added this to the 0.15.0 milestone Jun 16, 2014
@jreback jreback modified the milestones: 0.16.0, Next Major Release Mar 6, 2015
@gfyoung
Copy link
Member

gfyoung commented May 25, 2016

From what I can understand, memory_map differs in that files are mapped onto memory instead of being stored on disk. The code traces back to pandas/src/parser/io.c which includes files like sys/stat.h and sys/mman.h, whose info can be found in the Linux man pages. Thus, I don't even know if this actually applies to Windows for example. It's hard to tell since there is a fall-back if the memory map fails.

Not sure how many people out there use this option (it's not tested too much), and I don't feel comfortable enough writing an explanation about it. Probably someone with a better understanding of memory maps and those header files I mentioned could write something good.

@jreback
Copy link
Contributor Author

jreback commented Jun 8, 2016

closed by #13381

@jreback jreback closed this as completed Jun 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Docs IO CSV read_csv, to_csv IO Data IO issues that don't fit into a more specific label
Projects
None yet
Development

No branches or pull requests

2 participants