Skip to content
This repository has been archived by the owner on Sep 28, 2022. It is now read-only.

taxi import failing after ~150GB with OOM #110

Open
jaffee opened this issue Jan 30, 2019 · 1 comment
Open

taxi import failing after ~150GB with OOM #110

jaffee opened this issue Jan 30, 2019 · 1 comment

Comments

@jaffee
Copy link
Member

jaffee commented Jan 30, 2019

While doing some multi-cloud benchmarks, I noticed that the taxi import would use a "normal" (~10GB) amount of memory for a long time, and then suddenly over the course of about 90 seconds spike up and OOM even on boxes as large as 128GB.

It did not happen at the same point in the import each time - I observed it at 115.5GB, 159.6GB, 162.4GB, and 165.3GB among others.

I saw this happen both on AWS and Azure instances, but not OCI. The OCI instances I was using did have >200GB of RAM though - I did not measure their memory usage during operation to see if it spiked up over 128GB at any point.

@jaffee
Copy link
Member Author

jaffee commented Feb 7, 2019

I have now seen this on OCI as well on VM.Standard2.8 (120GB RAM), though it happened at something like 195GB ingested.

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

No branches or pull requests

1 participant