Skip to content
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

Memory fast filling #22

Open
gsvijayraajaa opened this issue Jun 15, 2016 · 3 comments
Open

Memory fast filling #22

gsvijayraajaa opened this issue Jun 15, 2016 · 3 comments

Comments

@gsvijayraajaa
Copy link

Hi,

I am trying to index a json file ( about 7GB) with 4 threads. The initial split in data to the threads fast fills the memory and the process gets killed automatically. I am running jsonpyes on AWS m4.xlarge instance. 

Regards,
Vijay Raajaa GS

@xros
Copy link
Owner

xros commented Jul 1, 2016

@gsvijayraajaa

what's the amount of your memory? Have you tried to use 2 threads? And what's the error log?

@xros
Copy link
Owner

xros commented Jul 1, 2016

And verifying data could be very time/memory consuming. You can separate this job by two processes. 1. Verify them somewhere 2. Then import them.

@xros
Copy link
Owner

xros commented Oct 18, 2016

@gsvijayraajaa Maybe now you can update jsonpyes to version 1.3.0 to test it.

#25

For memory safety, it's recommended that make some SWAP room before processing big data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants