-
Notifications
You must be signed in to change notification settings - Fork 77
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
Crash when running the latest docker image #20
Comments
This might have been caused by not having enough memory. We bumped our instance size up and are monitoring if any more crashes occur. |
Thank you for keeping us updated. We'll try to replicate it as well. |
Some updates here: Initially we ran XCMetrics including the Postgres DB + Redis on a T2.Micro (1 vCPU, 1 GiB memory). We saw crashes happening very frequently (every 10 minutes). We also saw out of memory errors in the logs and decided to upgrade We resized the instance to a T2.Medium now (2 vCPU, 4 GiB memory) and see a much stabler performance. The instance crashed once in a 24h hour window. The crash is now a different one which does not look like a memory crash but rather a crash inside the
Since it only happened once I don't think it is critical right now but we will keep monitoring it. @ecamacho We have a lot of jobs now that are in the DB marked as |
Interesting, not currently. We'll take a look, we may add one |
We started to see this crash quite often as increased the number of people reporting, so It may be resource-related. |
How big can be your .xcactivitylog file? Also, do you know if your project has a lot of Warnings or Notes? In #30 they are having memory-related issues due to a big number of notes in their logs |
It probably about 6Mb. As for warnings, about 120+ Warnings. Well bump the specs a bit and keep you posted. |
Hi there, I have similar issues with 2mb in size. What's the recommended specs? I tried with smaller project and it works. |
We are seeing a crash happening quite frequently which happens inside the Postgres stack. I am trying to investigate further where this crash is coming from.
The crash log:
The text was updated successfully, but these errors were encountered: