You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
seems to produce a nondeterministic mix of problems:
"Operation timed out after 900006 milliseconds with 0 bytes received" (on @XuedaShen's system)
Raising an error because of low bytes/sec (on my system)
(Potentially making the system unresponsive and then) getting killed by out-of-memory (OOM) killer (on my system). I'm estimating (from state data * rough # counties per state) that data as an object would be ~0.7GB, and as a JSON string is around ~1.5GB; my system as ~32GB RAM, with 8.5GB "free" at the moment, so hypothetically it should be able to handle it in RAM without OOM killing, but disk might be an option too.
The last one seems like something epidatr could potentially help out with; I've opened a companion issue there. The first two seem like potential API server issues or query performance issues.
Directly accessing the associated URL on Firefox is making progress, outputting a whole bunch of plaintext output; I assume at the end it will be formatted into a fancy json view, but I would prefer it to just save to a file when the output's this large. I assume there's some header that could be set to make this happen?
The text was updated successfully, but these errors were encountered:
This query
seems to produce a nondeterministic mix of problems:
The last one seems like something epidatr could potentially help out with; I've opened a companion issue there. The first two seem like potential API server issues or query performance issues.
Directly accessing the associated URL on Firefox is making progress, outputting a whole bunch of plaintext output; I assume at the end it will be formatted into a fancy json view, but I would prefer it to just save to a file when the output's this large. I assume there's some header that could be set to make this happen?
The text was updated successfully, but these errors were encountered: