<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://www.vokipedia.de/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="de">
		<id>http://www.vokipedia.de/index.php?action=history&amp;feed=atom&amp;title=What%E2%80%99s_All_That_Memory_For</id>
		<title>What’s All That Memory For - Versionsgeschichte</title>
		<link rel="self" type="application/atom+xml" href="http://www.vokipedia.de/index.php?action=history&amp;feed=atom&amp;title=What%E2%80%99s_All_That_Memory_For"/>
		<link rel="alternate" type="text/html" href="http://www.vokipedia.de/index.php?title=What%E2%80%99s_All_That_Memory_For&amp;action=history"/>
		<updated>2026-05-26T15:24:30Z</updated>
		<subtitle>Versionsgeschichte dieser Seite in Vokipedia</subtitle>
		<generator>MediaWiki 1.19.23</generator>

	<entry>
		<id>http://www.vokipedia.de/index.php?title=What%E2%80%99s_All_That_Memory_For&amp;diff=132869&amp;oldid=prev</id>
		<title>FlossiePouncy13 am 13. September 2025 um 13:00 Uhr</title>
		<link rel="alternate" type="text/html" href="http://www.vokipedia.de/index.php?title=What%E2%80%99s_All_That_Memory_For&amp;diff=132869&amp;oldid=prev"/>
				<updated>2025-09-13T13:00:57Z</updated>
		
		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;table class='diff diff-contentalign-left'&gt;
				&lt;col class='diff-marker' /&gt;
				&lt;col class='diff-content' /&gt;
				&lt;col class='diff-marker' /&gt;
				&lt;col class='diff-content' /&gt;
			&lt;tr valign='top'&gt;
			&lt;td colspan='2' style=&quot;background-color: white; color:black;&quot;&gt;← Nächstältere Version&lt;/td&gt;
			&lt;td colspan='2' style=&quot;background-color: white; color:black;&quot;&gt;Version vom 13. September 2025, 13:00 Uhr&lt;/td&gt;
			&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot;&gt;Zeile 1:&lt;/td&gt;
&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot;&gt;Zeile 1:&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class='diff-marker'&gt;−&lt;/td&gt;&lt;td style=&quot;background: #ffa; color:black; font-size: smaller;&quot;&gt;&lt;div&gt;&amp;lt;br&amp;gt;What’s all that &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;memory &lt;/del&gt;for? &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;Perhaps &lt;/del&gt;it’s for storing strings? &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;If &lt;/del&gt;you &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;really need &lt;/del&gt;to make use of the memory &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;in &lt;/del&gt;your laptop with Go-actually use it, with gigabytes of it allocated-then &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;chances are &lt;/del&gt;you&lt;del class=&quot;diffchange diffchange-inline&quot;&gt;'ll &lt;/del&gt;pay a &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;giant &lt;/del&gt;penalty for the Go rubbish collector (GC). However there are &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;issues &lt;/del&gt;you &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;are able to &lt;/del&gt;do about it. The Go GC checks what elements of the &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;[https://online-learning-initiative.org/wiki/index.php/User:Fay8387130114 Memory Wave] &lt;/del&gt;you have &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;allocated &lt;/del&gt;are still in use. It does this by &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;looking &lt;/del&gt;at all &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;of &lt;/del&gt;the memory for references to different &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;pieces &lt;/del&gt;of memory. If you’ve allotted &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;thousands and &lt;/del&gt;thousands of &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;items &lt;/del&gt;of memory, then all that ‘looking’ &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;necessarily &lt;/del&gt;takes some CPU time to do. So &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;if &lt;/del&gt;you truly need to use the gigabytes of memory in your &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;computer&lt;/del&gt;, you may wish to be &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;slightly careful &lt;/del&gt;about &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;how &lt;/del&gt;you do &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;things&lt;/del&gt;. How dangerous is it? Think about you have &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;got &lt;/del&gt;a &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;determined need &lt;/del&gt;to &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;remember &lt;/del&gt;one hundred million random 20 byte strings. What sort of overhead does the GC impose &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;if &lt;/del&gt;you &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;happen to &lt;/del&gt;do &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;this &lt;/del&gt;in a &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;traditional way&lt;/del&gt;?&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Here’s some code to allocate these strings. This &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;uses &lt;/del&gt;about 3.5 GB of RAM. So what impression does this have on GC? Nicely, one &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;straightforward thing &lt;/del&gt;we &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;will &lt;/del&gt;do to measure &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;this &lt;/del&gt;is &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;call &lt;/del&gt;the Go runtime to &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;force &lt;/del&gt;GC, and &lt;del class=&quot;diffchange diffchange-inline&quot;&gt; [https://gitea.mahss.io/caseykoontz992/memory-wave-program6016/wiki/%5BSolved%5D-your-Laptop-is-Low-on-Memory-Home-Windows-7%2F8%2F10-in-8-Ways Memory Wave] &lt;/del&gt;measure how &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;lengthy &lt;/del&gt;that takes. How &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;lengthy &lt;/del&gt;does that take? Oh. That’s &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;quite &lt;/del&gt;a long time. &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;Properly&lt;/del&gt;, it’s quite fast for &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;looking &lt;/del&gt;at a hundred million &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;issues &lt;/del&gt;(about 7ns a thing). However burning 700ms of CPU time every time the GC runs is unquestionably edging into the realm of &amp;quot;not ideal&amp;quot;. And if we run the GC once more, it takes approximately the identical time &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;again&lt;/del&gt;. 700ms of GC work each time the GC runs &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;till &lt;/del&gt;we’re &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;carried out &lt;/del&gt;with these strings. How can we &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;repair &lt;/del&gt;it? Luckily for us the Go GC is so intelligent that it doesn't &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;have &lt;/del&gt;a look at &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;every bit &lt;/del&gt;of &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;[https://www.reference.com/world-view/can-calculate-weighted-percentages-2b96671db80151e1?ad=dirN&amp;amp;qo=serpIndex&amp;amp;o=740005&amp;amp;origq=&lt;/del&gt;memory&lt;del class=&quot;diffchange diffchange-inline&quot;&gt;+allotted memory allotted]&lt;/del&gt;. If it knows the memory &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;does not contain &lt;/del&gt;any pointers, it doesn't &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;take &lt;/del&gt;a look at it.&amp;lt;br&amp;gt; &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Without pointers the memory &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;cannot &lt;/del&gt;be referencing &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;different items &lt;/del&gt;of memory, so the GC doesn’t want to look at it to &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;find out &lt;/del&gt;which memory is &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;not &lt;/del&gt;referenced and &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;therefore can &lt;/del&gt;be freed. If we &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;will &lt;/del&gt;arrange &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;things &lt;/del&gt;so we are able to &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;store &lt;/del&gt;the strings &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;with none &lt;/del&gt;pointers, we &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;can &lt;/del&gt;save this GC overhead. Oh, strings comprise pointers? &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;Yes&lt;/del&gt;, strings &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;comprise &lt;/del&gt;pointers. The reflect package &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;shows &lt;/del&gt;us what a string &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;truly &lt;/del&gt;is. A string is a pointer to a &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;bit &lt;/del&gt;of &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;[http://124.223.56.226:3000/declanangas420/5213715/wiki/Alzheimers%2C-Dementia-%26-Memory-Care-Facilities-In-Florida Memory Wave System] &lt;/del&gt;containing the bytes of the string, and a size of the string. So our slice of &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;a &lt;/del&gt;hundred million strings contains &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;100 &lt;/del&gt;million pointers and a hundred million lengths. And &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;a hundred &lt;/del&gt;million separate allocations which hold the bytes for the strings. As &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;a substitute &lt;/del&gt;of having &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;a hundred &lt;/del&gt;million separate allocations and &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;100 &lt;/del&gt;million pointers, we can allocate a single slice of bytes to contain all &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;of &lt;/del&gt;the bytes for all &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;of &lt;/del&gt;the strings, and make our &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;personal &lt;/del&gt;string-like objects that &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;comprise &lt;/del&gt;offsets into this slice.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;We define a string &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;bank &lt;/del&gt;to &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;include &lt;/del&gt;the string bytes. And &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;this &lt;/del&gt;is our &amp;quot;banked&amp;quot; version of a string with offsets as an alternative of pointers. We could make a function &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;so as &lt;/del&gt;to add a string to the string &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;bank &lt;/del&gt;and return a bankedString. This copies the bytes from the string into our string bank, and saves the offset of the string and the size of the string. This bankedString can then be used to retrieve the &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;original &lt;/del&gt;string. Storing our random strings &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;needs just just &lt;/del&gt;a little modification. If we now time GC we get a marked enchancment. This &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;is still quite &lt;/del&gt;a &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;very &lt;/del&gt;long time for GC, but if we run GC again we see an &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;extra huge &lt;/del&gt;drop. The first run of the GC frees up short-term strings we’ve created (slightly carelessly) whereas we build our slice of strings. &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;As soon as &lt;/del&gt;this is &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;finished&lt;/del&gt;, the GC overhead is practically nil. I doubt it &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;is smart &lt;/del&gt;to do this &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;type &lt;/del&gt;of factor &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;usually&lt;/del&gt;. It &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;solely actually is smart &lt;/del&gt;if you&lt;del class=&quot;diffchange diffchange-inline&quot;&gt;'re &lt;/del&gt;going to keep the strings for the lifetime of your course of as there’s no &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;technique &lt;/del&gt;to delete individual strings. What does this say about different &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;conditions&lt;/del&gt;? Perhaps you don’t &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;need &lt;/del&gt;to store &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;an enormous &lt;/del&gt;quantity of &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;knowledge&lt;/del&gt;. &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;Maybe &lt;/del&gt;you’re &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;constructing &lt;/del&gt;some sort of API service. Does this stuff apply? &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;Well&lt;/del&gt;, if &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;across &lt;/del&gt;all &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;of &lt;/del&gt;your goroutines and API handlers you &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;employ &lt;/del&gt;a &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;major &lt;/del&gt;quantity of RAM then &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;perhaps &lt;/del&gt;it does. If you &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;may &lt;/del&gt;keep away from using pointers &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;right &lt;/del&gt;here and there, &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;perhaps a few &lt;/del&gt;of your allocations will &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;end up &lt;/del&gt;being pointer-free, and this may &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;occasionally &lt;/del&gt;cut back the general CPU &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;utilization &lt;/del&gt;of the GC. Which &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;might &lt;/del&gt;make your program &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;carry out higher&lt;/del&gt;, or &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;price &lt;/del&gt;less to run. Simply &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;make &lt;/del&gt;sure you measure &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;things &lt;/del&gt;before and after any change to make &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;certain &lt;/del&gt;you &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;actually &lt;/del&gt;make an &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;improvement&lt;/del&gt;.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;When the BlackBerry debuted in 1999, carrying one was a hallmark of &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;highly effective &lt;/del&gt;executives and savvy technophiles. People who purchased one either needed or needed &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;fixed entry &lt;/del&gt;to e-mail, a calendar and a &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;phone&lt;/del&gt;. The BlackBerry's &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;manufacturer&lt;/del&gt;, &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;Research &lt;/del&gt;in Motion (RIM), reported &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;only &lt;/del&gt;25,000 &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;[https://dict.leo.org/?search=&lt;/del&gt;subscribers &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;subscribers] &lt;/del&gt;in that first yr. &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;But &lt;/del&gt;since then, its &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;popularity &lt;/del&gt;has skyrocketed. In September 2005, RIM reported 3.Sixty five million subscribers, and users describe being addicted to the &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;gadgets&lt;/del&gt;. The BlackBerry has even introduced new slang to the English language. There are &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;phrases &lt;/del&gt;for flirting &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;by way of &lt;/del&gt;BlackBerry (blirting), repetitive movement &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;injuries &lt;/del&gt;from &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;too much &lt;/del&gt;BlackBerry use (BlackBerry thumb) and unwisely using one's BlackBerry while intoxicated (drunk-Berrying). &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;While &lt;/del&gt;some individuals credit score the BlackBerry with letting them get out of the &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;office &lt;/del&gt;and spend time with &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;associates &lt;/del&gt;and &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;household&lt;/del&gt;, others accuse them of &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;permitting &lt;/del&gt;work to infiltrate each &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;moment &lt;/del&gt;of free time. We'll &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;also &lt;/del&gt;discover BlackBerry hardware and software. PDA. This &lt;del class=&quot;diffchange diffchange-inline&quot;&gt;may very well &lt;/del&gt;be time-consuming and inconvenient.&amp;lt;br&amp;gt;&lt;/div&gt;&lt;/td&gt;&lt;td class='diff-marker'&gt;+&lt;/td&gt;&lt;td style=&quot;background: #cfc; color:black; font-size: smaller;&quot;&gt;&lt;div&gt;&amp;lt;br&amp;gt;What’s all that &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;[https://myhomemypleasure.co.uk/wiki/index.php?title=User:ConcettaSimpson Memory Wave Experience] &lt;/ins&gt;for? &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;Maybe &lt;/ins&gt;it’s for storing strings? &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;In the event &lt;/ins&gt;you &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;truly want &lt;/ins&gt;to make use of the memory &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;on &lt;/ins&gt;your laptop with Go-actually use it, with gigabytes of it allocated-then you &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;could &lt;/ins&gt;pay a &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;big &lt;/ins&gt;penalty for &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt; [https://foutadjallon.com/index.php/Horizon_Adventurer_A_Thousand_Pocket_Memory_Mattress Memory Wave Experience] &lt;/ins&gt;the Go rubbish collector (GC). However there are &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;things &lt;/ins&gt;you &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;can &lt;/ins&gt;do about it. The Go GC checks what elements of the &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;memory &lt;/ins&gt;you &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;will &lt;/ins&gt;have &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;allotted &lt;/ins&gt;are still in use. It does this by &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;taking a look &lt;/ins&gt;at all the memory for references to different &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;items &lt;/ins&gt;of memory. If you’ve allotted &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;hundreds of &lt;/ins&gt;thousands of &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;pieces &lt;/ins&gt;of memory, then all that ‘looking’ &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;essentially &lt;/ins&gt;takes some CPU time to do. So &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;when &lt;/ins&gt;you truly need to &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;make &lt;/ins&gt;use &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;of &lt;/ins&gt;the gigabytes of memory in your &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;laptop&lt;/ins&gt;, you may wish to be &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;a bit of cautious &lt;/ins&gt;about &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;the way &lt;/ins&gt;you do &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;issues&lt;/ins&gt;. How dangerous is it? Think about you &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;might &lt;/ins&gt;have a &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;desperate want &lt;/ins&gt;to &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;recollect &lt;/ins&gt;one hundred million random 20 byte strings. What sort of overhead does the GC impose &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;when &lt;/ins&gt;you do &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;that &lt;/ins&gt;in a &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;standard manner&lt;/ins&gt;?&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Here’s some code to allocate these strings. This &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;makes use of &lt;/ins&gt;about 3.5 GB of RAM. So what impression does this have on GC? Nicely, one &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;easy factor &lt;/ins&gt;we &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;can &lt;/ins&gt;do to measure &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;that &lt;/ins&gt;is &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;name &lt;/ins&gt;the Go runtime to &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;pressure &lt;/ins&gt;GC, and measure how &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;long &lt;/ins&gt;that takes. How &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;long &lt;/ins&gt;does that take? Oh. That’s &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;fairly &lt;/ins&gt;a long time. &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;Nicely&lt;/ins&gt;, it’s quite fast for &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;taking a look &lt;/ins&gt;at a hundred million &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;things &lt;/ins&gt;(about 7ns a thing). However burning 700ms of CPU time every time the GC runs is unquestionably edging into the realm of &amp;quot;not ideal&amp;quot;. And if we run the GC once more, it takes approximately the identical time &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;once more&lt;/ins&gt;. 700ms of GC work each time the GC runs &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;until &lt;/ins&gt;we’re &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;accomplished &lt;/ins&gt;with these strings. How can we &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;fix &lt;/ins&gt;it? Luckily for us the Go GC is so intelligent that it doesn't &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;take &lt;/ins&gt;a look at &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;each piece &lt;/ins&gt;of memory &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;allocated&lt;/ins&gt;. If it knows the memory &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;doesn't include &lt;/ins&gt;any pointers, it doesn't &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;have &lt;/ins&gt;a look at it.&amp;lt;br&amp;gt;&lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;[https://tips-from-john.livejournal.com/ livejournal.com]&lt;/ins&gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Without pointers the &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;[http://giggetter.com/blog/135313/&lt;/ins&gt;memory&lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;-wave-the-ultimate-brainwave-entrainment-for-cognitive-enhancement/ Memory Wave] can't &lt;/ins&gt;be referencing &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;other pieces &lt;/ins&gt;of memory, so the GC doesn’t want to look at it to &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;determine &lt;/ins&gt;which memory is &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;no longer &lt;/ins&gt;referenced and &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;subsequently might &lt;/ins&gt;be freed. If we &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;are able to &lt;/ins&gt;arrange &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;issues &lt;/ins&gt;so we are able to &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;retailer &lt;/ins&gt;the strings &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;without any &lt;/ins&gt;pointers, we &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;will &lt;/ins&gt;save this GC overhead. Oh, strings comprise pointers? &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;Sure&lt;/ins&gt;, strings &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;contain &lt;/ins&gt;pointers. The reflect package &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;exhibits &lt;/ins&gt;us what a string &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;really &lt;/ins&gt;is. A string is a pointer to a &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;chunk &lt;/ins&gt;of &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;memory &lt;/ins&gt;containing the bytes of the string, and a size of the string. So our slice of &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;one &lt;/ins&gt;hundred million strings contains &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;one hundred &lt;/ins&gt;million pointers and a hundred million lengths. And &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;100 &lt;/ins&gt;million separate allocations which hold the bytes for the strings. As &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;an alternative &lt;/ins&gt;of having &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;100 &lt;/ins&gt;million separate allocations and &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;one hundred &lt;/ins&gt;million pointers, we can allocate a single slice of bytes to contain all the bytes for all the strings, and make our &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;own &lt;/ins&gt;string-like objects that &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;include &lt;/ins&gt;offsets into this slice.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;We define a string &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;financial institution &lt;/ins&gt;to &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;contain &lt;/ins&gt;the string bytes. And &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;that &lt;/ins&gt;is our &amp;quot;banked&amp;quot; version of a string with offsets as an alternative of pointers. We could make a function to add a string to the string &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;financial institution &lt;/ins&gt;and return a bankedString. This copies the bytes from the string into our string bank, and saves the offset of the string and the size of the string. This bankedString can then be used to retrieve the &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;unique &lt;/ins&gt;string. Storing our random strings &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;wants simply &lt;/ins&gt;a little &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;bit &lt;/ins&gt;modification. If we now time GC we get a marked enchancment. This &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;continues to be fairly &lt;/ins&gt;a long time for GC, but if we run GC again we see an &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;additional large &lt;/ins&gt;drop. The first run of the GC frees up short-term strings we’ve created (slightly carelessly) whereas we build our slice of strings. &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;Once &lt;/ins&gt;this is &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;completed&lt;/ins&gt;, the GC overhead is practically nil. I doubt it &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;makes sense &lt;/ins&gt;to do this &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;kind &lt;/ins&gt;of factor &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;normally&lt;/ins&gt;. It &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;only really makes sense &lt;/ins&gt;if you &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;are &lt;/ins&gt;going to keep the strings for the lifetime of your course of as there’s no &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;method &lt;/ins&gt;to delete individual strings. What does this say about different &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;situations&lt;/ins&gt;? Perhaps you don’t &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;wish &lt;/ins&gt;to store &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;a huge &lt;/ins&gt;quantity of &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;information&lt;/ins&gt;. &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;Perhaps &lt;/ins&gt;you’re &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;building &lt;/ins&gt;some sort of API service. Does this stuff apply? &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;Effectively&lt;/ins&gt;, if &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;throughout &lt;/ins&gt;all your goroutines and API handlers you &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;use &lt;/ins&gt;a &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;significant &lt;/ins&gt;quantity of RAM then &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;maybe &lt;/ins&gt;it does. If you &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;possibly can &lt;/ins&gt;keep away from using pointers here and &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt; [https://git.saike.fun:9755/macktritt98000 Memory Wave] &lt;/ins&gt;there, &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;maybe some &lt;/ins&gt;of your allocations will &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;find yourself &lt;/ins&gt;being pointer-free, and this may cut back the general CPU &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;usage &lt;/ins&gt;of the GC. Which &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;could &lt;/ins&gt;make your program &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;perform better&lt;/ins&gt;, or &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;value much &lt;/ins&gt;less to run. Simply &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;be &lt;/ins&gt;sure you measure &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;issues &lt;/ins&gt;before and after any change to make &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;sure &lt;/ins&gt;you &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;truly &lt;/ins&gt;make an &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;enchancment&lt;/ins&gt;.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;When the BlackBerry debuted in 1999, carrying one was a hallmark of &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;powerful &lt;/ins&gt;executives and savvy technophiles. People who purchased one either needed or needed &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;constant access &lt;/ins&gt;to e-mail, a calendar and a &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;cellphone&lt;/ins&gt;. The BlackBerry's &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;producer&lt;/ins&gt;, &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;Analysis &lt;/ins&gt;in Motion (RIM), reported &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;solely &lt;/ins&gt;25,000 subscribers in that first yr. &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;However &lt;/ins&gt;since then, its &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;recognition &lt;/ins&gt;has skyrocketed. In September 2005, RIM reported 3.Sixty five million subscribers, and users describe being addicted to the &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;units&lt;/ins&gt;. The BlackBerry has even introduced new slang to the English language. There are &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;words &lt;/ins&gt;for flirting &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;via &lt;/ins&gt;BlackBerry (blirting), repetitive movement &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;accidents &lt;/ins&gt;from &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;an excessive amount of &lt;/ins&gt;BlackBerry use (BlackBerry thumb) and unwisely using one's BlackBerry while intoxicated (drunk-Berrying). &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;Whereas &lt;/ins&gt;some individuals credit score the BlackBerry with letting them get out of the &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;workplace &lt;/ins&gt;and spend time with &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;friends &lt;/ins&gt;and &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;family&lt;/ins&gt;, others accuse them of &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;allowing &lt;/ins&gt;work to infiltrate each &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;second &lt;/ins&gt;of free time. We'll &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;additionally &lt;/ins&gt;discover BlackBerry hardware and software &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;program&lt;/ins&gt;. PDA. This &lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;could possibly &lt;/ins&gt;be time-consuming and inconvenient.&amp;lt;br&amp;gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/table&gt;</summary>
		<author><name>FlossiePouncy13</name></author>	</entry>

	<entry>
		<id>http://www.vokipedia.de/index.php?title=What%E2%80%99s_All_That_Memory_For&amp;diff=94616&amp;oldid=prev</id>
		<title>JosetteMarch5: Die Seite wurde neu angelegt: „&lt;br&gt;What’s all that memory for? Perhaps it’s for storing strings? If you really need to make use of the memory in your laptop with Go-actually use it, with…“</title>
		<link rel="alternate" type="text/html" href="http://www.vokipedia.de/index.php?title=What%E2%80%99s_All_That_Memory_For&amp;diff=94616&amp;oldid=prev"/>
				<updated>2025-08-10T11:32:33Z</updated>
		
		<summary type="html">&lt;p&gt;Die Seite wurde neu angelegt: „&amp;lt;br&amp;gt;What’s all that memory for? Perhaps it’s for storing strings? If you really need to make use of the memory in your laptop with Go-actually use it, with…“&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Neue Seite&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;lt;br&amp;gt;What’s all that memory for? Perhaps it’s for storing strings? If you really need to make use of the memory in your laptop with Go-actually use it, with gigabytes of it allocated-then chances are you'll pay a giant penalty for the Go rubbish collector (GC). However there are issues you are able to do about it. The Go GC checks what elements of the [https://online-learning-initiative.org/wiki/index.php/User:Fay8387130114 Memory Wave] you have allocated are still in use. It does this by looking at all of the memory for references to different pieces of memory. If you’ve allotted thousands and thousands of items of memory, then all that ‘looking’ necessarily takes some CPU time to do. So if you truly need to use the gigabytes of memory in your computer, you may wish to be slightly careful about how you do things. How dangerous is it? Think about you have got a determined need to remember one hundred million random 20 byte strings. What sort of overhead does the GC impose if you happen to do this in a traditional way?&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Here’s some code to allocate these strings. This uses about 3.5 GB of RAM. So what impression does this have on GC? Nicely, one straightforward thing we will do to measure this is call the Go runtime to force GC, and  [https://gitea.mahss.io/caseykoontz992/memory-wave-program6016/wiki/%5BSolved%5D-your-Laptop-is-Low-on-Memory-Home-Windows-7%2F8%2F10-in-8-Ways Memory Wave] measure how lengthy that takes. How lengthy does that take? Oh. That’s quite a long time. Properly, it’s quite fast for looking at a hundred million issues (about 7ns a thing). However burning 700ms of CPU time every time the GC runs is unquestionably edging into the realm of &amp;quot;not ideal&amp;quot;. And if we run the GC once more, it takes approximately the identical time again. 700ms of GC work each time the GC runs till we’re carried out with these strings. How can we repair it? Luckily for us the Go GC is so intelligent that it doesn't have a look at every bit of [https://www.reference.com/world-view/can-calculate-weighted-percentages-2b96671db80151e1?ad=dirN&amp;amp;qo=serpIndex&amp;amp;o=740005&amp;amp;origq=memory+allotted memory allotted]. If it knows the memory does not contain any pointers, it doesn't take a look at it.&amp;lt;br&amp;gt; &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Without pointers the memory cannot be referencing different items of memory, so the GC doesn’t want to look at it to find out which memory is not referenced and therefore can be freed. If we will arrange things so we are able to store the strings with none pointers, we can save this GC overhead. Oh, strings comprise pointers? Yes, strings comprise pointers. The reflect package shows us what a string truly is. A string is a pointer to a bit of [http://124.223.56.226:3000/declanangas420/5213715/wiki/Alzheimers%2C-Dementia-%26-Memory-Care-Facilities-In-Florida Memory Wave System] containing the bytes of the string, and a size of the string. So our slice of a hundred million strings contains 100 million pointers and a hundred million lengths. And a hundred million separate allocations which hold the bytes for the strings. As a substitute of having a hundred million separate allocations and 100 million pointers, we can allocate a single slice of bytes to contain all of the bytes for all of the strings, and make our personal string-like objects that comprise offsets into this slice.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;We define a string bank to include the string bytes. And this is our &amp;quot;banked&amp;quot; version of a string with offsets as an alternative of pointers. We could make a function so as to add a string to the string bank and return a bankedString. This copies the bytes from the string into our string bank, and saves the offset of the string and the size of the string. This bankedString can then be used to retrieve the original string. Storing our random strings needs just just a little modification. If we now time GC we get a marked enchancment. This is still quite a very long time for GC, but if we run GC again we see an extra huge drop. The first run of the GC frees up short-term strings we’ve created (slightly carelessly) whereas we build our slice of strings. As soon as this is finished, the GC overhead is practically nil. I doubt it is smart to do this type of factor usually. It solely actually is smart if you're going to keep the strings for the lifetime of your course of as there’s no technique to delete individual strings. What does this say about different conditions? Perhaps you don’t need to store an enormous quantity of knowledge. Maybe you’re constructing some sort of API service. Does this stuff apply? Well, if across all of your goroutines and API handlers you employ a major quantity of RAM then perhaps it does. If you may keep away from using pointers right here and there, perhaps a few of your allocations will end up being pointer-free, and this may occasionally cut back the general CPU utilization of the GC. Which might make your program carry out higher, or price less to run. Simply make sure you measure things before and after any change to make certain you actually make an improvement.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;When the BlackBerry debuted in 1999, carrying one was a hallmark of highly effective executives and savvy technophiles. People who purchased one either needed or needed fixed entry to e-mail, a calendar and a phone. The BlackBerry's manufacturer, Research in Motion (RIM), reported only 25,000 [https://dict.leo.org/?search=subscribers subscribers] in that first yr. But since then, its popularity has skyrocketed. In September 2005, RIM reported 3.Sixty five million subscribers, and users describe being addicted to the gadgets. The BlackBerry has even introduced new slang to the English language. There are phrases for flirting by way of BlackBerry (blirting), repetitive movement injuries from too much BlackBerry use (BlackBerry thumb) and unwisely using one's BlackBerry while intoxicated (drunk-Berrying). While some individuals credit score the BlackBerry with letting them get out of the office and spend time with associates and household, others accuse them of permitting work to infiltrate each moment of free time. We'll also discover BlackBerry hardware and software. PDA. This may very well be time-consuming and inconvenient.&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>JosetteMarch5</name></author>	</entry>

	</feed>