Have you tried increasing your permgen size? Loading our codebase uses up just about all of the default Java permgen, and when it gets close to out I believe I've seen it thrashing the GC on the main heap.
On Tuesday, June 17, 2014 6:38:46 AM UTC-7, Brian Marick wrote: > > > On Jun 16, 2014, at 2:57 PM, Daniel Compton <de...@danielcompton.net > <javascript:>> wrote: > > > You didn't mention whether this was on the free tier or a paid dyno. I > would expect the paid dynos to not be as heavily provisioned and could > possibly alleviate this. > > Paid. (And using 2X dynos didn't seem to make a difference.) > > -------- > Latest book: /Functional Programming for the Object-Oriented Programmer/ > https://leanpub.com/fp-oo > > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
