Skip to content
This repository has been archived by the owner on Jun 30, 2023. It is now read-only.

A2 made geocoding exorbitantly expensive #609

Closed
td928 opened this issue Nov 18, 2022 · 0 comments
Closed

A2 made geocoding exorbitantly expensive #609

td928 opened this issue Nov 18, 2022 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@td928
Copy link
Contributor

td928 commented Nov 18, 2022

After the enhancement of 22Q2 and A2 jobs added to the mix, it begins to seems that our data sync workflow would fail due to the sheer size of the number of records (more than 2 million with both bis and now).

I have some quick fixes implemented which seems to allow geocoding to finish but in the long run I do think it is worth to consider less the load and simplify the geocoding (see #597 #599) so we can both run devdb build more easily.

@td928 td928 added bug Something isn't working enhancement New feature or request labels Nov 18, 2022
@mbh329 mbh329 closed this as completed Apr 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants