Monitoring Client Memory Use

Solution Details - TPI 141289
https://www.ptc.com/appserver/cs/view/solution.jsp?n=141289
Solution Type
141289 TPI
Created Date 30-May-2008 Last Updated 11-Mar-2011
Title
Monitoring Client Memory Use
Details Description Various tools are available to monitor resource usage on Windows platforms. This document describes several techniques.
Additional Information
Real-time monitoring with the Windows Performance Monitor (perfmon): Startup Pro/ENGINEER, the Windchill Workgroup Manager or Browser process on the client machine Startup Windows Perfmon (Start > Run > perfmon > ok) Remove non-applicable counters (X button) if desired (Pages/sec, Avg. Disk Queue, % Processor, etc.) Select Add a Counter (+ button) Select Process in Performance object drop-down, Working Set in Select counters from list, xtop in Select instances from list (and/or uwgm_client.exe, iexplore.exe, firefox.exe), and Add button Repeat for Private Bytes and Virtual Bytes and select Close Right click the graph and select Properties In the System Monitor Properties Data tab, select each counter and set the scale to 0.000001. In the System Monitor Properties Graph tab, set the Maximum Vertical scale to 3000 Perfmon accurately shows how much memory the Pro/ENGINEER xtop, Windchill Workgroup Manager uwgm_client.exe, Internet Explorer iexplore.exe or Firefox firefox.exe process is using. The scale on the left is in MB. Pro/ENGINEER or other application will exit or return script erros when Virtual Bytes > 2000Mb (or 3000MB on 32-bit Windows w/3gb switch). Note: Working Set is the current size, in bytes, of the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before leaving main memory. This is the value reported in Windows Task Manager Mem Usage column. Private Bytes is the current size, in bytes, of memory that this process has allocated that cannot be shared with other processes. This is the value reported in Windows Task Manager VM Size column. Virtual Bytes is the current size, in bytes, of the virtual address space the process is using. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite, and the process can limit its ability to load libraries.
Real-time monitoring with Process Explorer: Download Process Explorer - http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx or http://download.sysinternals.com/Files/ProcessExplorer.zip
1 of 6
1/17/2012 10:56 AM
Extract the contents of the zip file to a directory Startup Process Explorer Collapse the System process tree Select View > Select Columns Select Private Bytes, Virtual Size and Ok from the Process Memory tab Process Explorer accurately reports memory usage
Background monitoring with Windows Performance Monitor (perfmon) Startup Pro/ENGINEER or other application on the client machine Startup Windows Perfmon (Start > Run > perfmon > ok) Select Performance Logs and Alerts > Counter Logs > New Log Settings Enter a new name > Ok Select Add Counters, select Process Performance Object, Working Set counter, xtop or other process, Add, repeat for Private Bytes, repeat for Virtual Bytes, select Close and Ok
The counter runs until stopped (will show as green when running)
Stop the counter and provide to Administrator for analysis along with client logs (i.e. trail.txt, std.out, uwgm.log) Note: Different sampling intervals can be used (i.e. 5 seconds)
Viewing counter log results on the same or other machine: Startup Windows Perfmon (Start > Run > perfmon > ok) Select the View Logfile Data button Select Log Files > Add > browse to and select the log that was previously generated > Ok Select the desired Time Range Add the desired counters from the Data tab In the System Monitor Properties Data tab, select each counter and set the scale to 0.000001. In the System Monitor Properties Graph tab, set the Maximum Vertical scale to 3000 Results for logging period displayed. Select Virtual Bytes, look at Maximum value and for spikes close to 2000Mb or 3000Mb
Configuring Windows Performance Monitor Alert to notifiy user when nearing virtual byte limit: Startup Pro/ENGINEER or other process on the client machine Startup Windows Perfmon (Start > Run > perfmon > ok) Select Console Root > Performance Logs and Alerts > Alerts in the left pane Select Action > New Alert Settings or the New Alert Settings button Type in proe_virtual_bytes > Ok Select Add in the General tab, Process performance object, Virtual bytes counter, xtop instance, Add, Close Change the "Alert when the value is" field to Over, change the Limit to 1850000000 (or 2850000000 for client with /3gb switch), Change the Sample data to every 60 seconds Select the Action tab, select the Log an entry in the application event log checkbox, Select the Send a network message to: checkbox, enter in your client hostname (You will need the windows messenger service running on your client for this to work) Start the Alert if it doesn't show as started (green) Check the Application Event Viewer log to make sure that the alert started ok When Pro/ENGINEER or other process reaches the limit specified, it will be logged to the event manager and the client receives a message that they are nearing the process limit
Note: When Virtual Bytes reaches ~1850Mb or ~2850MB on 32-bit Window with /3gb switch, it is good practice to restart Pro/ENGINEER or other application prior to running out of memory. See TPI 132948 (https://www.ptc.com/appserver/cs/view/solution.jsp?n=132948) for additional information as to what happens when running out of virtual memory. See TPI 111330 (http://www.ptc.com/appserver/cs/view/solution.jsp?n=111330) for additional information as to how to increase the per-process memory limit on Windows 32-bit.
2 of 6
1/17/2012 10:56 AM
See TPI 129658 (https://www.ptc.com/appserver/cs/view/solution.jsp?n=/129658.htm) for additional information as to how to use the PROE_MEMORY_BUFFER_SIZE config.pro option. This procedure is applicable to not only Pro/ENGINEER but other processes running on the client machine (Windchill Workgroup Manager, Web Browser, etc.).
Affected Products
Product Module Reported Release Pro/ENGINEER and Creo Elements/Pro Workgroup Manager for Pro/ENGINEER Wildfire Wildfire 2.0
Reported Datecode F000 Resolved Release Wildfire 2.0
Resolved Datecode F000 Affected Client Affected Server Product Module Reported Release Not Available Not Available Windchill PDMLink Performance 10.0
Reported Datecode F000 Resolved Release 10.0
Resolved Datecode F000 Affected Client Affected Server Product Module Reported Release Not Available Not Available Windchill PDMLink Workgroup Manager for Creo Elements/Direct Drafting 10.0
Resolved Datecode F000 Affected Client Affected Server Product Module Reported Release Not Available Not Available Windchill PDMLink Workgroup Manager for Arbortext IsoDraw 10.0
Resolved Datecode F000 Affected Client Not Available
3 of 6
1/17/2012 10:56 AM
Affected Server Product Module Reported Release
Not Available Windchill PDMLink Workgroup Manager for CADDS 10.0
Resolved Datecode F000 Affected Client Affected Server Product Module Reported Release Not Available Not Available Windchill PDMLink Workgroup Manager for CATIA V5 10.0
Resolved Datecode F000 Affected Client Affected Server Product Module Reported Release Not Available Not Available Windchill PDMLink Workgroup Manager for Unigraphics 10.0
Resolved Datecode F000 Affected Client Affected Server Product Module Reported Release Not Available Not Available Windchill PDMLink Workgroup Manager for Autodesk Inventor 10.0
Resolved Datecode F000 Affected Client Affected Server Product Module Not Available Not Available Windchill PDMLink Workgroup Manager for SolidWorks
4 of 6
1/17/2012 10:56 AM
Reported Release
10.0
Resolved Datecode F000 Affected Client Affected Server Product Module Reported Release Not Available Not Available Windchill PDMLink Workgroup Manager for Mathcad 10.0
Resolved Datecode F000 Affected Client Affected Server Product Module Reported Release Not Available Not Available Windchill PDMLink Workgroup Manager for Pro/ENGINEER Wildfire 10.0
Resolved Datecode F000 Affected Client Affected Server Product Module Reported Release Not Available Not Available Windchill PDMLink Workgroup Manager for AutoCAD 10.0
Resolved Datecode F000 Affected Client Affected Server Product Module Reported Release Not Available Not Available Windchill PDMLink Workgroup Manager for ECAD 10.0
Resolved Datecode F000
5 of 6
1/17/2012 10:56 AM
Affected Client Affected Server
Not Available Not Available
Related Documents
Type Number Status Description None Available
Copyright 2012, Parametric Technology Corporation
6 of 6
1/17/2012 10:56 AM

Monitoring Client Memory Use

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Monitoring Client Memory Use

Uploaded by

Copyright:

Available Formats

Solution Details - TPI 141289

Created Date 30-May-2008 Last Updated 11-Mar-2011