Title
l

lawjolla

07/04/2018, 8:11 PM
I'm using the Heroku dev deploy just to try it out, but the Prisma service just ran out of memory and I had to manually restart the dyno. I'm the only one using the service and didn't over request. Is there a memory leak? Is 500mb too small for Prisma?
2018-07-04T20:02:56.426466+00:00 app[web.1]: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
2018-07-04T20:02:56.426559+00:00 app[web.1]: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
2018-07-04T20:02:56.426718+00:00 app[web.1]: at java.lang.Thread.run(Thread.java:748)
2018-07-04T20:03:01.276041+00:00 heroku[web.1]: Process running mem=519M(101.4%)
2018-07-04T20:03:01.276145+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
h

harmony

07/04/2018, 8:27 PM
it's the jvm :^)
d

dpetrick

07/05/2018, 8:23 AM
What is the
Heroku dev deploy
? Generally speaking, low memory and Prisma is not a good idea, however, it should not crash like that with the correct JVM flags sets.
👍 1
l

lawjolla

07/05/2018, 5:41 PM
@dpetrick I'm new to Heroku and its CLI. Is that something I should be able to run? It's coming back as not a command
d

dpetrick

07/06/2018, 10:59 AM
Apologies, I was referring to your choice of words, how you are deploying Prisma. Is it using the Prisma Cloud Heroku flow?
l

lawjolla

07/06/2018, 7:30 PM
Yes. Just followed the Prisma tutorial and used their free tier.