Just to keep everyone informed, we’ve now had enough time back on Clojure 1.7.0 to rule out 1.8.0 as the source of our very slow memory leak.
Now we have the fun task of figuring out exactly what has introduced it :) Sean Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood From: Sean Corfield Date: Monday, August 17, 2015 at 7:50 PM To: <clojure@googlegroups.com> Subject: Re: [ANN] Clojure 1.8.0-alpha3 Clojure 1.8.0-alpha3 is now available. … Tuples have been disabled after further analysis of performance impacts. Out of curiosity, could this have surfaced in alpha2 as a memory leak? We had alpha2 in production for about a week and it looked like we were seeing a very slow memory leak. Our next production build was based on alpha4 and we have not seen that same memory curve (in a slightly longer period). Now that we’ve had longer in production, we are still seeing a slow memory leak. We are prepping to move back to 1.7.0 for the time being. If we don’t see the leak on 1.7.0 (so we can isolate the leak as coming from our code vs "your" code), we’ll put one server back on 1.8.0 Alpha 4 and see if we can identify what is actually leaking. Sean Corfield -- (904) 302-SEAN World Singles -- http://worldsingles.com/ -- 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.
