Skip to content

postgres high CPU usage! #5906

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
davisbra opened this issue Aug 11, 2019 · 4 comments
Closed

postgres high CPU usage! #5906

davisbra opened this issue Aug 11, 2019 · 4 comments
Labels
type:feature New feature or improvement of existing feature

Comments

@davisbra
Copy link

davisbra commented Aug 11, 2019

hi,
I use parse server with Postgres in my Node.js application. run parse (index.js) permanently in the background with pm2 My connection string in the app looks like this:

var api = new ParseServer({
  databaseURI: databaseUri || 'postgres://postgres:Pass@IPaddress:5432/DatabaseName' ,
 ...});

at first hours everything is ok and CPU usage is under 5% but after 10-12 hours it increases to 100% even when I didn’t make any requests and even queries to the database. when I restart the Postgres everything goes back to normal. do you know what may cause the problem?

  • Server

    • Operating System: ubuntu 16.04
    • Hardware: 8G RAM, CPU(s):3, CPU Model name:Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
    • Localhost or remote server? remote server
  • Database

    • Postgresql version: 11.4
    • Localhost or remote server? remote server
@dplewis
Copy link
Member

dplewis commented Aug 12, 2019

Can you check this thread #5029

@davisbra
Copy link
Author

thanks for your response, but I couldn't solve the problem!

@dplewis
Copy link
Member

dplewis commented Aug 14, 2019

What have you tried?
Did you remove pm2 in favor of cluster mode?
Where are you hosted, something could be pinging your server if you aren’t.

What version of Parse Server and Node are you running?

@stale
Copy link

stale bot commented Oct 5, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature New feature or improvement of existing feature
Projects
None yet
Development

No branches or pull requests

3 participants