Skip to content

Conversation

@missinglink
Copy link
Member

@missinglink missinglink commented Nov 7, 2017

DO NOT MERGE

This PR enables multicore support for the interpolation service.

I do not think this should be merged in its current state due to:

each process loads its own copy of 'node-postal', so each process will consume ~2GB of RAM.

We could consider defaulting to 1 process instead of os.cpus().length and then allow ops engineers to modify the setup to suit their environment using the CPUS env var.

Thoughts?

@dianashk
Copy link
Contributor

dianashk commented Nov 7, 2017

I think until we switch to using libpostal as a service we shouldn't merge this. It would just complicate things and we'd get more support questions than benefits.

@dianashk
Copy link
Contributor

Closing for the time being.

@dianashk dianashk closed this Nov 10, 2017
@ghost ghost removed the in review label Nov 10, 2017
@orangejulius
Copy link
Member

orangejulius commented May 20, 2018

We definitely should re-evaluate this after #146 is merged!

@orangejulius orangejulius reopened this May 20, 2018
@orangejulius orangejulius changed the title server: multicore WIP: server: multicore May 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants