Talk:Mono - Revision history

Nebadon at 05:37, 26 July 2009

2009-07-26T05:37:58Z

Nebadon at 04:46, 26 July 2009

2009-07-26T04:46:54Z

Nebadon at 04:28, 26 July 2009

2009-07-26T04:28:51Z

Nebadon at 04:12, 26 July 2009

2009-07-26T04:12:58Z

Grumly at 08:01, 17 June 2009

2009-06-17T08:01:59Z

Grumly at 07:19, 17 June 2009

2009-06-17T07:19:43Z

Grumly: /* the vshost.exe is not relevant in this scenario */

2009-06-17T07:18:39Z

‎the vshost.exe is not relevant in this scenario

Grumly: /* the vshost.exe is not relevant in this scenario */ new section

2009-06-17T07:18:19Z

‎the vshost.exe is not relevant in this scenario: new section

Morgaine at 20:04, 16 June 2009

2009-06-16T20:04:22Z

Morgaine at 16:11, 15 June 2009

2009-06-15T16:11:24Z

← Older revision		Revision as of 05:37, 26 July 2009
Line 49:		Line 49:
	* the .vshost.exe is not relevant in this scenario : The "opensim.vshost.exe" process is used by Visual Studio to allow enhanced debugging capabilities, i.e "edit and continue" and some other goodies (see [http://msdn.microsoft.com/en-us/library/ms185331%28VS.80%29.aspx MSDN documentation]). opensim.vshost.exe is completely unusefull to OpenSim in "production mode" and to worry about its 5mb overhead is not relevant IMHO. I think it might be interresting to test using a "release mode" compiled OpenSim, disabling all debugging options and setting the same optimization flags on in both Mono and .NET if it applies. As a bonus, here is a link that explains [http://shsc.info/WindowsMemoryManagement Memory management on Windows] which is more tricky than it seems.		* the .vshost.exe is not relevant in this scenario : The "opensim.vshost.exe" process is used by Visual Studio to allow enhanced debugging capabilities, i.e "edit and continue" and some other goodies (see [http://msdn.microsoft.com/en-us/library/ms185331%28VS.80%29.aspx MSDN documentation]). opensim.vshost.exe is completely unusefull to OpenSim in "production mode" and to worry about its 5mb overhead is not relevant IMHO. I think it might be interresting to test using a "release mode" compiled OpenSim, disabling all debugging options and setting the same optimization flags on in both Mono and .NET if it applies. As a bonus, here is a link that explains [http://shsc.info/WindowsMemoryManagement Memory management on Windows] which is more tricky than it seems.

−	* I can not agree with these test results they are not statistically sound and the tests performed are not a good usage case of ~~OpenSimualtor~~, these results should be ignored until proper testing can be performed and presented in a more consistent manner. - Nebadon Izumi	+	* I can not agree with these test results they are not statistically sound and the tests performed are not a good usage case of OpenSimulator, these results should be ignored until proper testing can be performed and presented in a more consistent manner. - Nebadon Izumi

← Older revision		Revision as of 04:46, 26 July 2009
Line 49:		Line 49:
	* the .vshost.exe is not relevant in this scenario : The "opensim.vshost.exe" process is used by Visual Studio to allow enhanced debugging capabilities, i.e "edit and continue" and some other goodies (see [http://msdn.microsoft.com/en-us/library/ms185331%28VS.80%29.aspx MSDN documentation]). opensim.vshost.exe is completely unusefull to OpenSim in "production mode" and to worry about its 5mb overhead is not relevant IMHO. I think it might be interresting to test using a "release mode" compiled OpenSim, disabling all debugging options and setting the same optimization flags on in both Mono and .NET if it applies. As a bonus, here is a link that explains [http://shsc.info/WindowsMemoryManagement Memory management on Windows] which is more tricky than it seems.		* the .vshost.exe is not relevant in this scenario : The "opensim.vshost.exe" process is used by Visual Studio to allow enhanced debugging capabilities, i.e "edit and continue" and some other goodies (see [http://msdn.microsoft.com/en-us/library/ms185331%28VS.80%29.aspx MSDN documentation]). opensim.vshost.exe is completely unusefull to OpenSim in "production mode" and to worry about its 5mb overhead is not relevant IMHO. I think it might be interresting to test using a "release mode" compiled OpenSim, disabling all debugging options and setting the same optimization flags on in both Mono and .NET if it applies. As a bonus, here is a link that explains [http://shsc.info/WindowsMemoryManagement Memory management on Windows] which is more tricky than it seems.

−	* I can not agree with these test results they are not statistically sound and the tests performed are not a good usage case of OpenSimualtor, these results should be ignored until proper testing can be performed and presented in a more ~~professional~~ manner. - Nebadon Izumi	+	* I can not agree with these test results they are not statistically sound and the tests performed are not a good usage case of OpenSimualtor, these results should be ignored until proper testing can be performed and presented in a more consistent manner. - Nebadon Izumi

← Older revision		Revision as of 04:28, 26 July 2009
Line 49:		Line 49:
	* the .vshost.exe is not relevant in this scenario : The "opensim.vshost.exe" process is used by Visual Studio to allow enhanced debugging capabilities, i.e "edit and continue" and some other goodies (see [http://msdn.microsoft.com/en-us/library/ms185331%28VS.80%29.aspx MSDN documentation]). opensim.vshost.exe is completely unusefull to OpenSim in "production mode" and to worry about its 5mb overhead is not relevant IMHO. I think it might be interresting to test using a "release mode" compiled OpenSim, disabling all debugging options and setting the same optimization flags on in both Mono and .NET if it applies. As a bonus, here is a link that explains [http://shsc.info/WindowsMemoryManagement Memory management on Windows] which is more tricky than it seems.		* the .vshost.exe is not relevant in this scenario : The "opensim.vshost.exe" process is used by Visual Studio to allow enhanced debugging capabilities, i.e "edit and continue" and some other goodies (see [http://msdn.microsoft.com/en-us/library/ms185331%28VS.80%29.aspx MSDN documentation]). opensim.vshost.exe is completely unusefull to OpenSim in "production mode" and to worry about its 5mb overhead is not relevant IMHO. I think it might be interresting to test using a "release mode" compiled OpenSim, disabling all debugging options and setting the same optimization flags on in both Mono and .NET if it applies. As a bonus, here is a link that explains [http://shsc.info/WindowsMemoryManagement Memory management on Windows] which is more tricky than it seems.

−	* I can not agree with these test results they are not ~~statisticlly~~ sound and the tests performed are not a good usage case of ~~opensimualtor~~, these results should be ignored until proper testing can be ~~preformed~~ and presented in a more professional manner. - Nebadon Izumi	+	* I can not agree with these test results they are not statistically sound and the tests performed are not a good usage case of OpenSimualtor, these results should be ignored until proper testing can be performed and presented in a more professional manner. - Nebadon Izumi

← Older revision		Revision as of 04:12, 26 July 2009
Line 48:		Line 48:

	* the .vshost.exe is not relevant in this scenario : The "opensim.vshost.exe" process is used by Visual Studio to allow enhanced debugging capabilities, i.e "edit and continue" and some other goodies (see [http://msdn.microsoft.com/en-us/library/ms185331%28VS.80%29.aspx MSDN documentation]). opensim.vshost.exe is completely unusefull to OpenSim in "production mode" and to worry about its 5mb overhead is not relevant IMHO. I think it might be interresting to test using a "release mode" compiled OpenSim, disabling all debugging options and setting the same optimization flags on in both Mono and .NET if it applies. As a bonus, here is a link that explains [http://shsc.info/WindowsMemoryManagement Memory management on Windows] which is more tricky than it seems.		* the .vshost.exe is not relevant in this scenario : The "opensim.vshost.exe" process is used by Visual Studio to allow enhanced debugging capabilities, i.e "edit and continue" and some other goodies (see [http://msdn.microsoft.com/en-us/library/ms185331%28VS.80%29.aspx MSDN documentation]). opensim.vshost.exe is completely unusefull to OpenSim in "production mode" and to worry about its 5mb overhead is not relevant IMHO. I think it might be interresting to test using a "release mode" compiled OpenSim, disabling all debugging options and setting the same optimization flags on in both Mono and .NET if it applies. As a bonus, here is a link that explains [http://shsc.info/WindowsMemoryManagement Memory management on Windows] which is more tricky than it seems.
		+
		+	* I can not agree with these test results they are not statisticlly sound and the tests performed are not a good usage case of opensimualtor, these results should be ignored until proper testing can be preformed and presented in a more professional manner. - Nebadon Izumi

← Older revision		Revision as of 08:01, 17 June 2009
Line 47:		Line 47:
	: Pastebin links reported to SL::AW Groupies by ssm2017 Binder, pasted here by [[User:Morgaine\|Morgaine]] 16:11, 15 June 2009 (UTC).		: Pastebin links reported to SL::AW Groupies by ssm2017 Binder, pasted here by [[User:Morgaine\|Morgaine]] 16:11, 15 June 2009 (UTC).

−	* the .vshost.exe is not relevant in this scenario : The "opensim.vshost.exe" process is used by Visual Studio to allow enhanced debugging capabilities, i.e "edit and continue" and some other goodies (see [http://msdn.microsoft.com/en-us/library/ms185331%28VS.80%29.aspx MSDN documentation]). opensim.vshost.exe is completely unusefull to OpenSim in "production mode" and to worry about its 5mb overhead is not relevant IMHO. I think it might be interresting to test using a "release mode" compiled OpenSim, disabling all debugging options and setting the same optimization flags on in both Mono and .NET if it applies.	+	* the .vshost.exe is not relevant in this scenario : The "opensim.vshost.exe" process is used by Visual Studio to allow enhanced debugging capabilities, i.e "edit and continue" and some other goodies (see [http://msdn.microsoft.com/en-us/library/ms185331%28VS.80%29.aspx MSDN documentation]). opensim.vshost.exe is completely unusefull to OpenSim in "production mode" and to worry about its 5mb overhead is not relevant IMHO. I think it might be interresting to test using a "release mode" compiled OpenSim, disabling all debugging options and setting the same optimization flags on in both Mono and .NET if it applies. As a bonus, here is a link that explains [http://shsc.info/WindowsMemoryManagement Memory management on Windows] which is more tricky than it seems.

@@ Line 47: / Line 47: @@
 : Pastebin links reported to SL::AW Groupies by ssm2017 Binder, pasted here by [[User:Morgaine|Morgaine]] 16:11, 15 June 2009 (UTC).
-the vshost.exe is not relevant in this scenario
+* the .vshost.exe is not relevant in this scenario : The "opensim.vshost.exe" process is used by Visual Studio to allow enhanced debugging capabilities, i.e "edit and continue" and some other goodies (see [http://msdn.microsoft.com/en-us/library/ms185331%28VS.80%29.aspx MSDN documentation]). opensim.vshost.exe is completely unusefull to OpenSim in "production mode" and to worry about its 5mb overhead is not relevant IMHO. I think it might be interresting to test using a "release mode" compiled OpenSim, disabling all debugging options and setting the same optimization flags on in both Mono and .NET if it applies.
-−
 The "opensim.vshost.exe" process is used by Visual Studio to allow enhanced debugging capabilities, i.e "edit and continue" and some other goodies (see [http://msdn.microsoft.com/en-us/library/ms185331%28VS.80%29.aspx MSDN documentation]).
 opensim.vshost.exe is completely unusefull to OpenSim in "production mode" and to worry about its 5mb overhead is not relevant IMHO.
 I think it might be interresting to test using a "release mode" compiled OpenSim, disabling all debugging options and setting the same optimization flags on in both Mono and .NET if it applies.

← Older revision		Revision as of 07:18, 17 June 2009
Line 46:		Line 46:

	: Pastebin links reported to SL::AW Groupies by ssm2017 Binder, pasted here by [[User:Morgaine\|Morgaine]] 16:11, 15 June 2009 (UTC).		: Pastebin links reported to SL::AW Groupies by ssm2017 Binder, pasted here by [[User:Morgaine\|Morgaine]] 16:11, 15 June 2009 (UTC).
		+
		+	== the vshost.exe is not relevant in this scenario ==
		+
		+	The "opensim.vshost.exe" process is used by Visual Studio to allow enhanced debugging capabilities, i.e "edit and continue" and some other goodies (see [http://msdn.microsoft.com/en-us/library/ms185331%28VS.80%29.aspx MSDN documentation]).
		+	opensim.vshost.exe is completely unusefull to OpenSim in "production mode" and to worry about its 5mb overhead is not relevant IMHO.
		+	I think it might be interresting to test using a "release mode" compiled OpenSim, disabling all debugging options and setting the same optimization flags on in both Mono and .NET if it applies.

← Older revision		Revision as of 20:04, 16 June 2009
Line 45:		Line 45:
	> [Miguel de Icaza]		> [Miguel de Icaza]

−	: Pastebin links reported to SL::AW Groupies by ssm2017 Binder. [[User:Morgaine\|Morgaine]] 16:11, 15 June 2009 (UTC)	+	: Pastebin links reported to SL::AW Groupies by ssm2017 Binder, pasted here by [[User:Morgaine\|Morgaine]] 16:11, 15 June 2009 (UTC).

← Older revision		Revision as of 16:11, 15 June 2009
Line 1:		Line 1:
	* It sure is nice that Opensim is on Miguel's radar now. He might even see it as a nice heavy load test for Mono, which would be good for the Opensim community. [[User:Morgaine\|Morgaine]] 23:18, 14 June 2009 (UTC)		* It sure is nice that Opensim is on Miguel's radar now. He might even see it as a nice heavy load test for Mono, which would be good for the Opensim community. [[User:Morgaine\|Morgaine]] 23:18, 14 June 2009 (UTC)
		+
		+	* Miguel's preceding post in [http://pastebin.ca/1460278 pastebin] may be worth preserving as well, as it provides some insight into which memory size parameter is actually being measured and compared (namely RSS), and why:
		+
		+	I did some testing and downloaded opensim-0.6.4-release on both Windows and Linux.
		+
		+	I accessed a remote Windows system to do the build and run the simulator and I used my
		+	local Linux machine with Hippo to test the memory usage. Sadly, Hippo kept crashing on me,
		+	so I could not do a very extensive test.
		+
		+	A fresh virtual world with Mono/32-bit vs Vista/32 bit has Mono using 51 megs of RAM on
		+	startup on Linux vs 55 megs of RAM on Vista (50 megs plus 5 megs of the OpenSim.vhost.exe)
		+
		+	If you run Mono/64 (which is what I initially did) the size of 64 bit pointeres has a strong
		+	effect on Mono and increases the process size by 11 megs.
		+
		+	So at least starting up, Mono ends up with a 5 meg advantage. Perhaps the objects loaded
		+	after that make a difference, but without the actual data that you used, it is hard to
		+	find out exactly what it is.
		+
		+	I suspect though, that you might have compared the memory usage report from taskmanager on Windows
		+	versus the VSIZE memory usage, this is a common mistake.
		+
		+	It is also worth pointing out that the VSIZE reported by ps aux is usually very large and is the
		+	wrong metric to measure memory usage of OpenSim on Mono. The VSIZE reports the VM address space
		+	used by Mono and it happens to include all sorts of things that are not actually using memory.
		+
		+	The RSS size is what you want to look at in both cases. There are a few hundred blogs that explain
		+	why you should not use VSIZE when computing memory usage and why you should look at RSS, for instance:
		+
		+	http://virtualthreads.blogspot.com/2006/02/understanding-memory-usage-on-linux.html
		+
		+	[Miguel]
		+	-----------
		+	> First Post:
		+	>
		+	> Regarding the claims on Mono’s memory problems. I would like to know what exactly you claim
		+	> that is larger in Mono than it is on .NET.
		+	>
		+	> I can understand a small percentage increase in memory consumption in Mono, but not a 3x or
		+	> 4x increase in memory usage.
		+	>
		+	> Could you provide a sample “set” that I could use to test various versions of Mono across a
		+	> number of operating systems and compare it to Windows?
		+	> [Miguel de Icaza]
		+
		+	: Pastebin links reported to SL::AW Groupies by ssm2017 Binder. [[User:Morgaine\|Morgaine]] 16:11, 15 June 2009 (UTC)