Page MenuHomeSoftware Heritage

entrypoints: ensure guncorn services can handle more than one connection
ClosedPublic

Authored by douardda on Jun 27 2019, 10:39 AM.

Diff Detail

Repository
rCDFD Dockerfiles for developers
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

douardda created this revision.Jun 27 2019, 10:39 AM
vlorentz requested changes to this revision.Jun 27 2019, 7:56 PM
vlorentz added a subscriber: vlorentz.

bad indent + typo in the commit message

This revision now requires changes to proceed.Jun 27 2019, 7:56 PM

Otherwise what's the point of using gunicorn...

To give more details.
As an example, if we list something and by luck we start loading a huge repository... then the storage cannot handle both adding new data in the model and allow another connection from other services, say for example the web app ;)

douardda updated this revision to Diff 5545.Jun 28 2019, 10:48 AM

fixes according to vlorentz' comment

Otherwise what's the point of using gunicorn...

To give more details.
As an example, if we list something and by luck we start loading a huge repository... then the storage cannot handle both adding new data in the model and allow another connection from other services, say for example the web app ;)

my point exactly

vlorentz accepted this revision.Jun 28 2019, 11:39 AM
This revision is now accepted and ready to land.Jun 28 2019, 11:39 AM
This revision was automatically updated to reflect the committed changes.