Skip to content

2.7.2 has a huge impact on latency #4616

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
SebC99 opened this issue Mar 9, 2018 · 8 comments
Closed

2.7.2 has a huge impact on latency #4616

SebC99 opened this issue Mar 9, 2018 · 8 comments

Comments

@SebC99
Copy link
Contributor

SebC99 commented Mar 9, 2018

Issue Description

When updating parse-server from 2.7.1 to 2.7.2 there's a huge impact on server latency (observed on AWS ELB)

The chart below presents the increase (at the exact minute of the update) and the decrease one week later when coming back to 2.7.1 (no other changes)

capture d ecran 2018-03-09 a 11 50 40

Environment Setup

  • Server

    • parse-server version: Upgrading 2.7.1 to 2.7.2
    • Operating System: Nodejs with AWS ElasticBeanstalk on t2.large
  • Database

    • MongoDB version: 3.6
    • Storage engine: WiredTiger
    • Localhost or remote server? Mongo Atlas
@steven-supersolid
Copy link
Contributor

steven-supersolid commented Mar 9, 2018

There's a bug in mongodb-core 3.0.x that was fixed in 3.0.4 https://github.com/mongodb-js/mongodb-core/blob/v3.0.4/HISTORY.md which is fixed in the corresponding 3.0.4 node.js driver https://github.com/mongodb/node-mongodb-native/blob/v3.0.4/HISTORY.md

The bug is increased latency (about double) on mongodb SSL connections.

parse-server 2.7.2 upgraded the driver from 2.1.17 in 2.7.1 to 3.0.1 so likely had the bug introduced there

#4603 updates the driver to 3.0.4 so will fix this in the next release

@JacobJT
Copy link

JacobJT commented Mar 9, 2018

Could this affect CPU usage on EC2 as well? I.e. longer requests results in more requests staying active and waiting for their results?

@flovilmart
Copy link
Contributor

@JacobJT it’s unlikely that waiting for something spiked CPU usage. The SSL bug may have caused the CPU spike

@JacobJT
Copy link

JacobJT commented Mar 9, 2018

Still this same issue with Mongo, or are you referring to a different issue with SSL?

I suppose a more to the point question: Does 2.7.2 also affect CPU spikes, and reverting to 2.7.1 would reduce / eliminate them until 2.7.3 is released?

@SebC99
Copy link
Contributor Author

SebC99 commented Mar 9, 2018

@JacobJT in my case, there could be a 10% CPU increase linked to 2.7.2 but that's not that clear.

@JacobJT
Copy link

JacobJT commented Mar 9, 2018

@SebC99 Thanks for the info. We had a CPU spike + massive latency, but it doesn't look like it matched up with our deployment of 2.7.2, I think it was related to some marketing e-mails causing a user spike and EB not spinning up a new server instance fast enough to handle it.

@flovilmart
Copy link
Contributor

flovilmart commented Mar 10, 2018

2.7.4 has been released, please update and reopen the issue if it persists.

@SebC99
Copy link
Contributor Author

SebC99 commented Mar 12, 2018

I confirm 2.7.4 fixes the issues, no more latency increase, just perfect :)

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

No branches or pull requests

4 participants