-
Notifications
You must be signed in to change notification settings - Fork 51
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
Reservation failure #41
Comments
I think the computer just run out of RAM memory... |
I agree, looks like you're out of memory. What are your server system specs like - how much RAM? What is the |
@connormanning. I had a 4 GB ram computer with 1 GB cacheSize (2 vCPU). |
@connormanning any ideas? Thanks! |
You might try lowering your You should also add your machine's instance store as swap space. For the
The mounts might be different on the |
thank you, @connormanning I will let you know soon how it went. |
Hello @connormanning. There is something going on that I noticed. Greyhound does not release the RAM memory after use. For example, if I use Greyhound to serve a 300 MM points model and it uses 4GB of RAM, the same RAM remain occupied forever, even after closing the app. This RAM memory usage then stacks along multiple models. For example, If I serve a different model, 4GB of RAM more will be occupied and so on, limiting the number of models to be able to serve. What can I do to make it clean the RAM memory? Thanks. |
Hello @connormanning. Could you please guide me through what could be this issue? Thanks! I get the following error at some point during serving a 300M point cloud.
Exception in pool task: std::bad_alloc
16:07:02:11 LOG Error handling: { code: 400, message: 'Reservation failure' }
The text was updated successfully, but these errors were encountered: