Performance problem about ogr2ogr

[wavded]

Hey @1Map, what Node version are you using, and are you possibly running out of memory? The 502 error is odd, I don't know what would return that, are you going through a proxy to get to the database?

[1Map]

Hi @wavded ,

I am using nodejs 6.11.4. My NodeJS app is using express and is behind NGINX Reverse Proxy. I have clients that uses the app to download data as shape files. The moment a client start a lenghty job the whole web app becomes unresponsive giving 502 errors on every other call. This is also not a memory issue as I have enough memory.

I also uses Uptime Robot to monitor my HTTP. The moment a lengthy job starts, then I will suddenly also receive emails from Uptime Robot informing me that my website is down.

[wavded]

Is the client making one large call, or multiple ones? Perhaps the thread pool is hung up waiting on ogr2ogr to return. I'm assuming the process is hung at 100% during this time. You may want to use cluster: https://nodejs.org/api/cluster.html to get more out of the server. If you have anything duplicable I could check on my side. At this point I'm guessing.

[1Map]

Hi @wavded

No, this can be one single client accessing one single large call to ogr2ogr with no other clients online, and then it can get hung up.

[wavded]

Hmm, is the NGINX timeout too short? Seems like ogr2ogr is still processing.

[1Map]

@wavded Thanks for the help so far. Where exactly can I start looking for this in NGINX ?

What I can say is the following: The app is stable if ogr2ogr is not running. The moment ogr2ogr kicks in and do lengthy job, then all becomes unstable. The moment ogr2ogr finishes the job, then all is back to normal (without restarting any service). Also, the 502 errors (while ogr2ogr is processing) is intermittent and not the whole time.

Also, I create an ogr2ogr job in the background and immediately return a response to the client. It is not that the client have to wait for the job to finish to get a response.

[wavded]

Closing due to age, reopen if issue persists.