Re: [OPEN-ILS-GENERAL] Client 2.3.0 grabbing and not releasing memory
I used Evergreen Staff Client for some fire-testing on Xulrunner 16. Just update the application.ini file to accept a newer version. -- David Busby Edoceo, Inc. http://edoceo.com/ 206.282.6500 On Tue, Dec 4, 2012 at 12:53 PM, Bob Wicksall bwicks...@pls-net.org wrote: Snip Taking a different tack, Jason Etheridge suggests asking circ staff who seem to be hitting this problem the worst this question: by chance are you keeping you entire morning check-in history in the on-screen list (not using Trim List)? We just had a library check two of their circ computers. The Evergreen process was at 649Meg and 578Meg and they had 5 items or less in the check-in history. This is Evergreen 2.2.X Bob Wicksall Systems Administrator Pioneer Library System 2557 State Rt. 21 Canandaigua, New York 14424 Voice: (585) 394-8260 Fax: (585) 394-1935 - Original Message - From: Galen Charlton g...@esilibrary.com To: Evergreen Discussion Group open-ils-general@list.georgialibraries.org Sent: Tuesday, December 4, 2012 11:46:00 AM Subject: Re: [OPEN-ILS-GENERAL] Client 2.3.0 grabbing and not releasing memory Hi Bob, On Mon, Dec 3, 2012 at 8:38 AM, Bob Neeper neepe...@oplin.org wrote: The only solution so far has been to completely exit the client many, many times during the day. Our director said Saturday, the East CIRC (Has the most activity) client took so much ram he had to kill the process. A bug has been opened on Launchpad for gathering information about potential memory leaks in the staff client. One of the points raised so far in that bug is a question worth asking your circ staff: Taking a different tack, Jason Etheridge suggests asking circ staff who seem to be hitting this problem the worst this question: by chance are you keeping you entire morning check-in history in the on-screen list (not using Trim List)? Regards, Galen -- Galen Charlton Director of Implementation Equinox Software, Inc. / The Open Source Experts email: g...@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org http://evergreen-ils.org
Re: [OPEN-ILS-GENERAL] Client 2.3.0 grabbing and not releasing memory
Hi Bob, On Mon, Dec 3, 2012 at 8:38 AM, Bob Neeper neepe...@oplin.org wrote: The only solution so far has been to completely exit the client many, many times during the day. Our director said Saturday, the East CIRC (Has the most activity) client took so much ram he had to kill the process. A bug has been opened on Launchpad for gathering information about potential memory leaks in the staff client. One of the points raised so far in that bug is a question worth asking your circ staff: Taking a different tack, Jason Etheridge suggests asking circ staff who seem to be hitting this problem the worst this question: by chance are you keeping you entire morning check-in history in the on-screen list (not using Trim List)? Regards, Galen -- Galen Charlton Director of Implementation Equinox Software, Inc. / The Open Source Experts email: g...@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web:http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org http://evergreen-ils.org
Re: [OPEN-ILS-GENERAL] Client 2.3.0 grabbing and not releasing memory
On Dec 4, 2012 8:46 AM, Galen Charlton g...@esilibrary.com wrote: Hi Bob, On Mon, Dec 3, 2012 at 8:38 AM, Bob Neeper neepe...@oplin.org wrote: The only solution so far has been to completely exit the client many, many times during the day. Our director said Saturday, the East CIRC (Has the most activity) client took so much ram he had to kill the process. A bug has been opened on Launchpad for gathering information about potential memory leaks in the staff client. One of the points raised so far in that bug is a question worth asking your circ staff: Taking a different tack, Jason Etheridge suggests asking circ staff who seem to be hitting this problem the worst this question: by chance are you keeping you entire morning check-in history in the on-screen list (not using Trim List)? Also note that xulrunner 15 addressed some longstanding memory leak issues - and as we're on 14 currently, it might be worth trying out a more current version for the sake of comparison to see if that makes a difference. http://m.cnet.com/news/firefox-15-remembers-to-forget-old-memory/57501454?ds=1
Re: [OPEN-ILS-GENERAL] Client 2.3.0 grabbing and not releasing memory
Snip Taking a different tack, Jason Etheridge suggests asking circ staff who seem to be hitting this problem the worst this question: by chance are you keeping you entire morning check-in history in the on-screen list (not using Trim List)? We just had a library check two of their circ computers. The Evergreen process was at 649Meg and 578Meg and they had 5 items or less in the check-in history. This is Evergreen 2.2.X Bob Wicksall Systems Administrator Pioneer Library System 2557 State Rt. 21 Canandaigua, New York 14424 Voice: (585) 394-8260 Fax: (585) 394-1935 - Original Message - From: Galen Charlton g...@esilibrary.com To: Evergreen Discussion Group open-ils-general@list.georgialibraries.org Sent: Tuesday, December 4, 2012 11:46:00 AM Subject: Re: [OPEN-ILS-GENERAL] Client 2.3.0 grabbing and not releasing memory Hi Bob, On Mon, Dec 3, 2012 at 8:38 AM, Bob Neeper neepe...@oplin.org wrote: The only solution so far has been to completely exit the client many, many times during the day. Our director said Saturday, the East CIRC (Has the most activity) client took so much ram he had to kill the process. A bug has been opened on Launchpad for gathering information about potential memory leaks in the staff client. One of the points raised so far in that bug is a question worth asking your circ staff: Taking a different tack, Jason Etheridge suggests asking circ staff who seem to be hitting this problem the worst this question: by chance are you keeping you entire morning check-in history in the on-screen list (not using Trim List)? Regards, Galen -- Galen Charlton Director of Implementation Equinox Software, Inc. / The Open Source Experts email: g...@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org http://evergreen-ils.org
[OPEN-ILS-GENERAL] Client 2.3.0 grabbing and not releasing memory
Title: Email Signature Our two front desk CIRC PC's are: Windows XP-Pro 32bit Core2 Duo E4600, 2.4GHz, 1024MB PC2-5300 SDRAM, 80gb 7200RPM HD Purchased August 2008 They worked fine with the previous Evergreen version. The consortium was upgraded to version 2.3.0 (client also) November 18, 2012 Staff has been complaining they need to reboot the CIRC PC's as they get slow, stop etc. Not being able to talk my way out, I started observing the problem. Watching Windows Task Manager, the Evergreen.exe process is not releasing memory. At one point it had grabbed over 650mb of ram on our East CIRC A simple log in /out test showed the client kept grabbing large chunks of ram. Also learned another COOL library is having the same problem with their XP PC's. It was suggested to try the next client 2.3.1 which I put on a third PC to test. This PC was recently rebuilt and not yet in service. Running the same log in /our test, produced the same memory grab. This morning I observed another creeping memory problem in a static situation. So I ran the same tests on a Windows7 PC for comparison. PC is i5-650 3.2GHz 4096MB PC3-10600 SDRAM 640GB 7200RPM HD Simple Log in / out test 22,404k Opened client login screen 52,272k After login and main screen opened 28,140k After Clicking on X to close main screen 49,448k After Clicking log off 61,412k After log in and main screen opened again 59,024k After Clicking on X to close main screen 59,028k After Clicking log off 71,176k After log in and main screen opened again 68,268k After Clicking on X to close main screen 68,288k After Clicking log off 79,752k After log in and main screen opened again Simple Static test. Clicked checkout on tab1 Entered patron card number and clicked submit Clicked + for new tab and clicked Check In Clicked + for new tab and clicked Item Status Made tab2 'Item Check In' active and watched the Task Manager 114,240k at 09:20 AM and started climbing 158,832k at 10:08 AM 126,244k at 10:15 AM Went down since last check 140,060k at 10:24 AM 150,300k at 10:31 AM 154,764k at 10:33 AM 164,732k at 10:40 AM 120,068k at 10:47 AM Went down since last check 153,872k at 11:07 AM Two main XP CIRC's, during normal check in / out use this morning West CIRC East CIRC 326,280k 207,400k at 10:45 AM 343,720k 258,304k at 10:56 AM 379,300k 300,676k at 11:07 AM Cataloging PC from yesterday (Same specs as Windows 7 PC) 11/30/12 09:44 327,900k 11/30/12 12:16 340,256k 11/30/12 05:21 427,412k The only solution so far has been to completely exit the client many, many times during the day. Our director said Saturday, the East CIRC (Has the most activity) client took so much ram he had to kill the process. Suggestions ? -- -- R. W. (Bob) Neeper Community Library 44 Burrer Dr. Map Sunbury, Oh 43074 Tel: (740)-965-3901
Re: [OPEN-ILS-GENERAL] Client 2.3.0 grabbing and not releasing memory
Title: Email Signature Hi Bob, Unfortunately this is not the first time I've heard of issues with Evergreen 2.3+ and memory management. Previously, memory problems had been reported sporadically even while we were on 2.0, but since our upgrade to 2.3 the number of reports from libraries has jumped significantly. We're still attempting to replicate / look for the source of the problem, but it seems (from stories reported) that higher circulating library PCs are hitting memory issues sooner than other departments. Alternatively, we've observed that other departments in the libraries tend to close out of Evergreen on a more regular basis and doing so sometimes resets Evergreen's memory usage down to a proper level. At present time, we've asked libraries affected to institute some sort of regular restarting process to their workflows to try keeping usage down, but it is definitely still a problem. It's also affecting only a small subset of machines in the libraries, so only 1 or 2 circ machines break down while the others are just fine. Curious to hear from other Evergreen systems running 2.3 (or greater) experiencing issues, but if we haven't already I think it's time we filed an official Evergreen bug on the subject to track discussion/troubleshooting efforts. -- Ben On 12/03/2012 11:38 AM, Bob Neeper wrote: Our two front desk CIRC PC's are: Windows XP-Pro 32bit Core2 Duo E4600, 2.4GHz, 1024MB PC2-5300 SDRAM, 80gb 7200RPM HD Purchased August 2008 They worked fine with the previous Evergreen version. The consortium was upgraded to version 2.3.0 (client also) November 18, 2012 Staff has been complaining they need to reboot the CIRC PC's as they get slow, stop etc. Not being able to talk my way out, I started observing the problem. Watching Windows Task Manager, the Evergreen.exe process is not releasing memory. At one point it had grabbed over 650mb of ram on our East CIRC A simple log in /out test showed the client kept grabbing large chunks of ram. Also learned another COOL library is having the same problem with their XP PC's. It was suggested to try the next client 2.3.1 which I put on a third PC to test. This PC was recently rebuilt and not yet in service. Running the same log in /our test, produced the same memory grab. This morning I observed another creeping memory problem in a static situation. So I ran the same tests on a Windows7 PC for comparison. PC is i5-650 3.2GHz 4096MB PC3-10600 SDRAM 640GB 7200RPM HD Simple Log in / out test 22,404k Opened client login screen 52,272k After login and main screen opened 28,140k After Clicking on X to close main screen 49,448k After Clicking log off 61,412k After log in and main screen opened again 59,024k After Clicking on X to close main screen 59,028k After Clicking log off 71,176k After log in and main screen opened again 68,268k After Clicking on X to close main screen 68,288k After Clicking log off 79,752k After log in and main screen opened again Simple Static test. Clicked checkout on tab1 Entered patron card number and clicked submit Clicked + for new tab and clicked Check In Clicked + for new tab and clicked Item Status Made tab2 'Item Check In' active and watched the Task Manager 114,240k at 09:20 AM and started climbing 158,832k at 10:08 AM 126,244k at 10:15 AM Went down since last check 140,060k at 10:24 AM 150,300k at 10:31 AM 154,764k at 10:33 AM 164,732k at 10:40 AM 120,068k at 10:47 AM Went down since last check 153,872k at 11:07 AM Two main XP CIRC's, during normal check in / out use this morning West CIRC East CIRC 326,280k 207,400k at 10:45 AM 343,720k 258,304k at 10:56 AM 379,300k 300,676k at 11:07 AM Cataloging PC from yesterday (Same specs as Windows 7 PC) 11/30/12 09:44 327,900k 11/30/12 12:16 340,256k 11/30/12 05:21 427,412k The only solution so far has been to completely exit the client many, many times during the day. Our director said Saturday, the East CIRC (Has the most activity) client took so much ram he had to kill the process. Suggestions ? -- -- R. W. (Bob) Neeper Community Library 44 Burrer Dr. Map Sunbury, Oh 43074 Tel: (740)-965-3901 -- Benjamin Shum Open Source Software Coordinator Bibliomation, Inc. 32 Crest Road Middlebury, CT 06762 203-577-4070, ext. 113
Re: [OPEN-ILS-GENERAL] Client 2.3.0 grabbing and not releasing memory
Title: Email Signature Good day everybody. We are in the same consortium as Bob, and running 2.3.1 client. We have been open to the public for about 2 3/4 hours today, and our primary circ computers are showing 542,750k memory usage and 641,500k respectively on a moderately busy morning. My staff are not complaining about slowness, but they're using i3 systems with 4GB of DDR3 and Win7 Pro. So nearly new computers, and all they are using them for most of the time is Evergreen and three or four firefox tabs... I will bear this in mind though, because my staff had mentioned something about slowness a few weeks ago, but I assumed it was gremlins or a couple of people downloading ISOs on our public computers at the time.. So perhaps many others are getting the same results, but just don't notice it often enough for it to be an issue...? Thanks. Joe Joseph Knueven Director Germantown Public Library 51 N. Plum St. Germantown, OH 45327 937-855-4001 knuev...@oplin.org On 12/3/2012 12:22 PM, Ben Shum wrote: Hi Bob, Unfortunately this is not the first time I've heard of issues with Evergreen 2.3+ and memory management. Previously, memory problems had been reported sporadically even while we were on 2.0, but since our upgrade to 2.3 the number of reports from libraries has jumped significantly. We're still attempting to replicate / look for the source of the problem, but it seems (from stories reported) that higher circulating library PCs are hitting memory issues sooner than other departments. Alternatively, we've observed that other departments in the libraries tend to close out of Evergreen on a more regular basis and doing so sometimes resets Evergreen's memory usage down to a proper level. At present time, we've asked libraries affected to institute some sort of regular restarting process to their workflows to try keeping usage down, but it is definitely still a problem. It's also affecting only a small subset of machines in the libraries, so only 1 or 2 circ machines break down while the others are just fine. Curious to hear from other Evergreen systems running 2.3 (or greater) experiencing issues, but if we haven't already I think it's time we filed an official Evergreen bug on the subject to track discussion/troubleshooting efforts. -- Ben On 12/03/2012 11:38 AM, Bob Neeper wrote: Our two front desk CIRC PC's are: Windows XP-Pro 32bit Core2 Duo E4600, 2.4GHz, 1024MB PC2-5300 SDRAM, 80gb 7200RPM HD Purchased August 2008 They worked fine with the previous Evergreen version. The consortium was upgraded to version 2.3.0 (client also) November 18, 2012 Staff has been complaining they need to reboot the CIRC PC's as they get slow, stop etc. Not being able to talk my way out, I started observing the problem. Watching Windows Task Manager, the Evergreen.exe process is not releasing memory. At one point it had grabbed over 650mb of ram on our East CIRC A simple log in /out test showed the client kept grabbing large chunks of ram. Also learned another COOL library is having the same problem with their XP PC's. It was suggested to try the next client 2.3.1 which I put on a third PC to test. This PC was recently rebuilt and not yet in service. Running the same log in /our test, produced the same memory grab. This morning I observed another creeping memory problem in a static situation. So I ran the same tests on a Windows7 PC for comparison. PC is i5-650 3.2GHz 4096MB PC3-10600 SDRAM 640GB 7200RPM HD Simple Log in / out test 22,404k Opened client login screen 52,272k After login and main screen opened 28,140k After Clicking on X to close main screen 49,448k After Clicking log off 61,412k After log in and main screen opened again 59,024k After Clicking on X to close main screen 59,028k After Clicking log off 71,176k After log in and main screen opened again 68,268k After Clicking on X to close main screen 68,288k After Clicking log off 79,752k After log in and main screen opened again Simple Static test. Clicked checkout on tab1 Entered patron card number and clicked submit Clicked + for new tab and clicked Check In Clicked + for new tab and clicked Item Status Made tab2 'Item Check In'
