On Fri, Jan 25, 2013 at 10:41 AM, Hilton Gibson <[email protected]> wrote: > Since upgrading to DSpace 1.8.2 in Dec/Jan the memory is climbing radically. > Does anybody else experience this. What can cause it?
I don't know, if I knew I would have reported it as a bug :) But here's how I would proceed. I would find a tool to display objects on the heap, grouped by class name and sorted by size. That might help identify the offending class(es). Something like this: http://docs.oracle.com/javase/6/docs/technotes/guides/visualvm/images/heapdump-classes-screen.png Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
