monitor virtual memory used by xtop.exe

[folle76]

ogni tanto sperimento un crash improvviso di creo 1.0 parametric m20. non c'è un assieme o una parte in particolare che provoca il crash. generalmente accade quando ho un bel po' di file in sessione.
adesso ho provato ad implementare la soluzione tpi 141289:

"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"

in teoria dovrebbe darmi un allarme prima del crash per esaurimento della memoria virtuale così faccio a tempo a salvare su disco un po' di roba. spesso quando si riapre creo da un crash non sempre si riparte dal punto in cui lo si lasciato (anche nel caso di file salvati): e questa è decisamente la cosa meno simpatica.
qualcuno ha già provato ad implementare quel tipo di soluzione?
grazie.

 

[nicksoft]

ogni tanto sperimento un crash improvviso di creo 1.0 parametric m20. non c'è un assieme o una parte in particolare che provoca il crash. generalmente accade quando ho un bel po' di file in sessione.
adesso ho provato ad implementare la soluzione tpi 141289:

"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"

in teoria dovrebbe darmi un allarme prima del crash per esaurimento della memoria virtuale così faccio a tempo a salvare su disco un po' di roba. spesso quando si riapre creo da un crash non sempre si riparte dal punto in cui lo si lasciato (anche nel caso di file salvati): e questa è decisamente la cosa meno simpatica.
qualcuno ha già provato ad implementare quel tipo di soluzione?
grazie.

we constantly monitor that value (even if we do it with a program developed internally) so as to alert the user that the limit is approaching.
in your case I wanted to ask you if you already put the switch to 3gb (if you have a 32-bit operating system) because it raises the threshold in which it will crash...

 

[DANI-3D]

... you already put the switch to 3gb (if you have a 32-bit operating system) because it raises the threshold in which it will crash...

Hi, Nick.
Maybe you're referring to this http://www.cad3d.it/forum1/showthread.php?t=15910 ?
or is another method. I'm interested in that.

 

[nicksoft]

Hi, Nick.
Maybe you're referring to this http://www.cad3d.it/forum1/showthread.php?t=15910 ?
or is another method. I'm interested in that.

Yeah, same thing.
obviously use a s.o. 64-bit solves this problem completely, but since there are still many 32-bit systems and we can't change all computers at once:wink:, the only one is precautionary by increasing the maximum size that the process can have.

I remember that this is a limit of 32-bit operating systems, even if you have installed 3-4 gb ram, a single process will not exceed 2gb (or 3gb with the switch).

Since sometimes with the 3gb switch there may be problems because other programs or drivers crash, I recommend setting the value a little below 3gb.

It is explained here: http://support.microsoft.com/kb/316739practically the switch becomes /3gb /userva=2900 (click the user if you have strange behaviors of the pc!)

 

[Parametric_Ozzy]

Yeah, same thing.
obviously use a s.o. 64-bit solves this problem completely, but since there are still many 32-bit systems and we can't change all computers at once:wink:, the only one is precautionary by increasing the maximum size that the process can have.

I remember that this is a limit of 32-bit operating systems, even if you have installed 3-4 gb ram, a single process will not exceed 2gb (or 3gb with the switch).

Since sometimes with the 3gb switch there may be problems because other programs or drivers crash, I recommend setting the value a little below 3gb.

It is explained here: http://support.microsoft.com/kb/316739practically the switch becomes /3gb /userva=2900 (click the user if you have strange behaviors of the pc!)

exact was a limit of windows xp 32 bits, at least if you mounted 4 gb of ram you could see them ...:smile: