WoW:Lua object memory sizes - Revision history

Bear: /* Function closures */

2023-10-13T16:05:43Z

Function closures

← Older revision		Revision as of 16:05, 13 October 2023
Line 55:		Line 55:
	Each function closure takes 20 bytes of RAM. The below code will use 20000 bytes:		Each function closure takes 20 bytes of RAM. The below code will use 20000 bytes:
	<pre>		<pre>
	for t=1,1000		for t=1,1000 do
	x = function() end		x = function() end
	end		end
Line 62:		Line 62:
	<pre>		<pre>
	local semistatic = "hi!"		local semistatic = "hi!"
	for t=1,1000		for t=1,1000 do
	x = function() print(semistatic) end		x = function() print(semistatic) end
	end		end
Line 68:		Line 68:
	However, upvalues that actually ''change'' use an additional 32 bytes. The below code will use 20000 + 4000 + 32000 = 56000 bytes:		However, upvalues that actually ''change'' use an additional 32 bytes. The below code will use 20000 + 4000 + 32000 = 56000 bytes:
	<pre>		<pre>
	for t=1,1000		for t=1,1000 do
	x = function() print(t) end		x = function() print(t) end
	end		end
Line 74:		Line 74:
	And finally, a mix: The below code will use 202500 + 42500 + 32*500 = 40000 bytes		And finally, a mix: The below code will use 202500 + 42500 + 32*500 = 40000 bytes
	<pre>		<pre>
	for t=1,500		for t=1,500 do
	for i=1,2		for i=1,2 do
	x = function() print(t) end		x = function() print(t) end
	end		end
	end		end
	</pre>		</pre>

2023-10-13T16:04:19Z

Function closures

← Older revision		Revision as of 16:04, 13 October 2023
Line 74:		Line 74:
	And finally, a mix: The below code will use 202500 + 42500 + 32*500 = 40000 bytes		And finally, a mix: The below code will use 202500 + 42500 + 32*500 = 40000 bytes
	<pre>		<pre>
	for t=1,~~'''~~500~~'''~~		for t=1,500
	for i=1,2		for i=1,2
	x = function() print(t) end		x = function() print(t) end

2023-10-13T16:03:58Z

Function closures

← Older revision		Revision as of 16:03, 13 October 2023
Line 60:		Line 60:
	</pre>		</pre>
	Upvalues that do not change only uses 4 bytes per closure. The below code will use 20000 + 4000 = 24000 bytes:		Upvalues that do not change only uses 4 bytes per closure. The below code will use 20000 + 4000 = 24000 bytes:
			<pre>
	local semistatic = "hi!"		local semistatic = "hi!"
	for t=1,1000		for t=1,1000
	x = function() print(semistatic) end		x = function() print(semistatic) end
	end		end
			</pre>
	However, upvalues that actually ''change'' use an additional 32 bytes. The below code will use 20000 + 4000 + 32000 = 56000 bytes:		However, upvalues that actually ''change'' use an additional 32 bytes. The below code will use 20000 + 4000 + 32000 = 56000 bytes:
	for t=1,1000		<pre>
			for t=1,1000
	x = function() print(t) end		x = function() print(t) end
	end		end
			</pre>
	And finally, a mix: The below code will use 202500 + 42500 + 32*500 = 40000 bytes		And finally, a mix: The below code will use 202500 + 42500 + 32*500 = 40000 bytes
			<pre>
	for t=1,'''500'''		for t=1,'''500'''
	for i=1,2		for i=1,2
Line 76:		Line 79:
	end		end
	end		end
			</pre>

2023-10-13T16:02:30Z

Function closures

← Older revision		Revision as of 16:02, 13 October 2023
Line 54:		Line 54:

	Each function closure takes 20 bytes of RAM. The below code will use 20000 bytes:		Each function closure takes 20 bytes of RAM. The below code will use 20000 bytes:
			<pre>
	for t=1,1000		for t=1,1000
	x = function() end		x = function() end
	end		end
			</pre>
	Upvalues that do not change only uses 4 bytes per closure. The below code will use 20000 + 4000 = 24000 bytes:		Upvalues that do not change only uses 4 bytes per closure. The below code will use 20000 + 4000 = 24000 bytes:
	local semistatic = "hi!"		local semistatic = "hi!"

2023-08-15T04:48:34Z

Move page script moved page Lua object memory sizes to Lua object memory sizes without leaving a redirect

← Older revision

Revision as of 04:48, 15 August 2023

2010-04-26T12:05:01Z

nav tag

← Older revision		Revision as of 12:05, 26 April 2010
Line 1:		Line 1:
			{{uitech}}
	Lua contains a fairly small set of data structures. This page aims to document how much size each structure uses, to aid addon programmers with memory optimization.		Lua contains a fairly small set of data structures. This page aims to document how much size each structure uses, to aid addon programmers with memory optimization.

2010-02-02T02:28:46Z

Quiz!

← Older revision		Revision as of 02:28, 2 February 2010
Line 74:		Line 74:
	end		end
	end		end

	~~== Quiz! ==~~

	~~To motivate programmers, here follows a number of statements. Only one is correct. If you choose the right one, you will be shown boobies ([[wikipedia:NSFW\|NSFW]]).~~

	* [http://www.disney.com/ It is better to have lots of named keys in a table rather than create a sub-table with integer indices]
	* [http://www.ratemyboobies.com/ It usually uses less CPU power to let the incremental GC handle tables compared to recycling them]
	* [http://www.disney.com/ It is always better to use lots of upvalues to a function closure because locals don't use any memory]

	~~[[Category:UI technical details]]~~

2008-07-07T21:14:01Z

← Older revision		Revision as of 21:14, 7 July 2008
Line 83:		Line 83:
	* [http://www.disney.com/ It is always better to use lots of upvalues to a function closure because locals don't use any memory]		* [http://www.disney.com/ It is always better to use lots of upvalues to a function closure because locals don't use any memory]

	[[Category:UI ~~Technical Details~~]]		[[Category:UI technical details]]

2007-12-14T03:13:22Z

Quiz!: Added a link to describe NSFW

← Older revision		Revision as of 03:13, 14 December 2007
Line 77:		Line 77:
	== Quiz! ==		== Quiz! ==

	To motivate programmers, here follows a number of statements. Only one is correct. If you choose the right one, you will be shown boobies.		To motivate programmers, here follows a number of statements. Only one is correct. If you choose the right one, you will be shown boobies ([[wikipedia:NSFW\|NSFW]]).

	* [http://www.disney.com/ It is better to have lots of named keys in a table rather than create a sub-table with integer indices]		* [http://www.disney.com/ It is better to have lots of named keys in a table rather than create a sub-table with integer indices]

2007-07-16T06:29:32Z

Function closures: Better explanation of changing vs unchanging values

@@ Line 49: / Line 49: @@
 == Function closures ==
 Each function closure takes 20 bytes of RAM. The below code will use 20000 bytes:
@@ Line 55: / Line 57: @@
   end
-Each upvalue uses an additional 36 bytes of RAM for integers/booleans/refs. The below code will use 20000 + 36000 = 56000 bytes:
+Upvalues that do not change only uses 4 bytes per closure. The below code will use 20000 + 4000 = 24000 bytes:
   for t=1,1000
     x = function() print(t) end
   end
 [[Category:UI Technical Details]]