It is in part a cop-out. Windows may not always reclaim memory from a service when it shrinks its memory. Also a service simply may not shrink its memory. I do not know which is the case here. We have always used the CAD to stop and start the scheduler as needed to avoid this problem. The CAD does not increase its memory usage so it does not suffer from either problem. Also, when trending memory usage be sure to track page file usage and free memory, Windows will page inactive code as needed. Also, if there is several GB free your level of urgency may change.
Andy Huebner -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Zoltan Forray/AC/VCU Sent: Monday, January 03, 2011 3:09 PM To: [email protected] Subject: [ADSM-L] Memory usage issues with "traditional scheduler service" on Windows I have a client/admin complaining about excessive memory usage by the client scheduler, since upgrading the client from 6.1.2.0 to 6.2.2.0. Before, dsmcsvc.exe was using around 21mb. Now it is using from 178mb (today) to spiking over 1gb. They did some digging and found various articles/docs that talks about using the CAD/managedservices to help reduce the memory footprint. One thing that disturbs me is the statement "Tip: Restart the traditional scheduler periodically to free system resources previously used by system calls.". You can read this here: http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/index.jsp?topic=/com.ibm.itsm.client.doc/t_cfg_schdcad.html This sounds like a cop-out to address memory leaks. How many of you "restart the scheduler service periodically to free system resources"? Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services [email protected] - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
