Skip to content
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

What's the system requirement and limitations? #10

Open
mcfriend99 opened this issue Jan 15, 2024 · 6 comments
Open

What's the system requirement and limitations? #10

mcfriend99 opened this issue Jan 15, 2024 · 6 comments

Comments

@mcfriend99
Copy link

The app keeps getting on my ubuntu deployment killed due to system out of memory when running as CLI in foreground or background as well as when running as a daemon.

It will be nice to let us know the minimum system requirement.

@Wouimbly
Copy link

Yo, i'm using a nuc i5 12g, 64g ram, 2to disk... i ran the swap api in a docker and with the binary. i had to allow 48g of ram for the service to run properly... even tho if i stop it and restart it i'll get an oom too.
So clean ubuntu 22.x restart with 8cores, 48g ram it runs ok... less than that == oom after few minutes

@paadoks
Copy link

paadoks commented Feb 17, 2024

image I suggest getting 50+ Gb. Couldn't start it on 48.

@mcfriend99
Copy link
Author

Really appreciate the recommendation. Please can anyone @Wouimbly and @paadoks can you guys answer three other questions for me?

  • Is the $500 minimum liquidity is still required before a token can be part of the token list and/or swapped on the self-hosted API?
  • Which RPC provider are you using with it that supports the yellowstone plugin?? I tried Helius, but it's very slow compared to Quicknode in my tests, and the quicknode team never got back to me on my question of whether the yellowstone grpc plugin is enabled on their nodes.
  • Is it great for sniping tokens?? I understand this will also depend somewhat on question number 1 in some ways.

Really appreciated your answers and will appreciate this more.

Guess the Jupiter team can do a better work with documenting the answer to the general questions of system requirements and question number 1.

Thanks

@mcfriend99 mcfriend99 changed the title What's the system requirement? What's the system requirement and limitations? Feb 17, 2024
@paadoks
Copy link

paadoks commented Feb 23, 2024

@mcfriend99
I've only tried to run jup API in non-recommended mode, without Yellowstone. I've heard, that with Yellowstone it won't consume so much RAM.
Regarding your questions, I won't be much of a help :(

@Lusitaniae
Copy link

Lusitaniae commented Feb 23, 2024

7.4Gb RAM using Yellowstone grpc colocated with the validator, but CPU usage is quite high

image

What causes such high CPU usage? This is running on same hardware used for RPC nodes:

  • AMD EPYC 7543P 32-Core Processor
  • 64 threads

@Daice
Copy link

Daice commented May 18, 2024

To set up your own Jupiter-swap API, what are the requirements for the RPC? Does the RPC need to have account-index?

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

5 participants