Skip to content
This repository was archived by the owner on Nov 6, 2020. It is now read-only.

Is there any way to run parity with less memory? #5407

Closed
georgek146 opened this issue Apr 5, 2017 · 3 comments
Closed

Is there any way to run parity with less memory? #5407

georgek146 opened this issue Apr 5, 2017 · 3 comments
Labels
Z1-question 🙋‍♀️ Issue is a question. Closer should answer.

Comments

@georgek146
Copy link

I am trying to run parity on a low memory vps, and I am getting fatal runtime error: out of memory. Is there any way that I could run parity with less memory? If not how much memory do I need to be able to reliably run it?

@5chdn 5chdn added the Z1-question 🙋‍♀️ Issue is a question. Closer should answer. label Apr 6, 2017
@5chdn
Copy link
Contributor

5chdn commented Apr 6, 2017

How much memory do you have available?

You can use --cache 16 which reduces the internal caching in memory to a minimum of 16MB.

@tomusdrw
Copy link
Collaborator

tomusdrw commented Apr 6, 2017

Also try this:
--pruning-history 16 --pruning-memory 16, but note this will cause your node to be unable to handle more than 16 blocks long forks.

What version are you running and which network you're trying to sync with?

@5chdn
Copy link
Contributor

5chdn commented May 9, 2017

Closing as answered. Might be related to #4694 or #4439

@5chdn 5chdn closed this as completed May 9, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Z1-question 🙋‍♀️ Issue is a question. Closer should answer.
Projects
None yet
Development

No branches or pull requests

3 participants