Closed Rogibb111 closed 1 year ago
Update on this, it seems that now whenever I try to scrape, I hit my memory limit and the machine kills the java process running the app. I'm guessing I will have to solve this issue first before addressing the issue above (if it is still occurring),
First steps to trying to debug this will probably be to see what the memory profile is on my local machine, and see if there is anything I can do in my app to clamp down on memory. Not sure if there is a way in Scala/Java to tune the JVM to use up less memory if possible. It looks like you can monitor the JVM instance using jvisualvm
. Need to find out where that lives on my machine.
To debug the above issue, I used both VisualVM and EclipseMAT to do some analysis on the heap stack that my application is using. I couldn't find anything out of the ordinary accept that when running my app in production, it has a much smaller memory footprint than when it runs on fly.io. I am creating a new issue for this here.
When I hit the scraping endpoint to run the scraper in production (Fly.io), I am seeing an error in the logs when the A-Basin scraper is run. The error is as follows: