<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Santiance &#187; Tip</title>
	<atom:link href="http://santiance.com/tag/tip/feed/" rel="self" type="application/rss+xml" />
	<link>http://santiance.com</link>
	<description>Kristopher Ives&#039;s Developer Notes</description>
	<lastBuildDate>Wed, 28 Jul 2010 10:07:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Tip: CPU Scaling Performance</title>
		<link>http://santiance.com/2009/10/tip-cpu-scaling-performance/</link>
		<comments>http://santiance.com/2009/10/tip-cpu-scaling-performance/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 19:56:15 +0000</pubDate>
		<dc:creator>Kristopher Ives</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Applet]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[Flash]]></category>
		<category><![CDATA[GNOME]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Tip]]></category>

		<guid isPermaLink="false">http://santiance.com/?p=493</guid>
		<description><![CDATA[There is a GNOME Applet included by default in Ubuntu that allows you to adjust your CPU scaling frequency, which most hardware supports. You can right click any panel and select Add to Panel, then select the CPU Frequency Scaling Monitor applet. This is a misleading name because it does more than just monitor the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://santiance.com/wp-content/uploads/cpu-scaling.png"><img class="alignright size-full wp-image-494" title="CPU Scaling" src="http://santiance.com/wp-content/uploads/cpu-scaling.png" alt="CPU Scaling" width="147" height="222" /></a>There is a GNOME Applet included by default in Ubuntu that allows you to adjust your CPU scaling frequency, which most hardware supports. You can right click any panel and select <em>Add to Panel</em>, then select the <strong>CPU Frequency Scaling Monitor</strong> applet.</p>
<p>This is a misleading name because it does more than just <em>monitor</em> the scaling, it allows you to change it easily. Most people disregard these settings because many settings like this don&#8217;t make a huge difference in other applications. There is one place it makes a big difference, which is the mother of all CPU users: Web Flash-based video. This thing basically physically abuses your processor. You can use <a title="Flash Benchmarking 101" href="http://arstechnica.com/software/news/2008/10/benchmarking-flash-player-10.ars" target="_blank">flash little performance tests</a> to get an idea of how CPU scaling affects your hardware.</p>
<p>In the same way, I find that actually making use of the <em>Powersave</em> and other options when on battery. On desktop systems where power consumption isn&#8217;t an issue, this setting will always be set at <em>Performance</em>. While <em>Ondemand</em> is rather good for typical use, some users find that it degrades response-time for things like <em><a title="Compiz Related Articles" href="http://santiance.com/tag/compiz/" target="_self">Compiz</a></em>.</p>
<p>Also remember that <em>IOWait</em> is typically the bottleneck for a lot of applications. I chose to use Flash as an example because it does a poor job of accomplishing it&#8217;s job and as a result requires a magnitude of additional computational power. You can easily compare the amount of processor usage to anything like <em>VLC</em>, <em>Totem</em>, or <em>Mplayer</em> and they will be a fraction of the usage.</p>
]]></content:encoded>
			<wfw:commentRss>http://santiance.com/2009/10/tip-cpu-scaling-performance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tip: Force your GNOME panel to reload</title>
		<link>http://santiance.com/2009/08/tip-force-your-gnome-panel-to-reload/</link>
		<comments>http://santiance.com/2009/08/tip-force-your-gnome-panel-to-reload/#comments</comments>
		<pubDate>Tue, 11 Aug 2009 10:28:40 +0000</pubDate>
		<dc:creator>Kristopher Ives</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[GNOME]]></category>
		<category><![CDATA[Tip]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://67.43.13.30/~kives/wp/?p=117</guid>
		<description><![CDATA[If you&#8217;ve installed a GNOME Applet, but you can&#8217;t see it in the Add menu, then you&#8217;ll either have to reload gnome-panel or wait a while. Reloading isn&#8217;t the cleanest thing, but you can do it by executingkillall gnome-panel and then gnome-panel via ALT+F2. Doing this in a normal terminal isn&#8217;t advised, because if that [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;ve installed a GNOME Applet, but you can&#8217;t see it in the <em>Add</em> menu, then you&#8217;ll either have to reload gnome-panel or wait a while. Reloading isn&#8217;t the cleanest thing, but you can do it by executing<code>killall gnome-panel</code> and then <code>gnome-panel</code> via ALT+F2.</p>
<p>Doing this in a normal terminal isn&#8217;t advised, because if that shell is terminated it would also end the panel process. However, if you can get around that by using <code>nohup gnome-panel</code>, or using the bash keyword <code>disown</code> after having ran the process in that terminal.</p>
]]></content:encoded>
			<wfw:commentRss>http://santiance.com/2009/08/tip-force-your-gnome-panel-to-reload/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tip: Append to an array with + operator</title>
		<link>http://santiance.com/2009/08/tip-append-to-an-array-with/</link>
		<comments>http://santiance.com/2009/08/tip-append-to-an-array-with/#comments</comments>
		<pubDate>Sat, 08 Aug 2009 15:37:01 +0000</pubDate>
		<dc:creator>Kristopher Ives</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Tip]]></category>

		<guid isPermaLink="false">http://67.43.13.30/~kives/wp/?p=52</guid>
		<description><![CDATA[You can use the addition and increment operators in PHP to concatenate arrays. For example, $c = $a + $b; If you&#8217;ve used array_merge() to do this in the past, it&#8217;s important to note the difference between merging arrays and concatenating them. When you merge they keys are used to determine how the resulting array [...]]]></description>
			<content:encoded><![CDATA[<p>You can use the addition and increment operators in PHP to concatenate arrays. For example, <code>$c = $a + $b;</code></p>
<p>If you&#8217;ve used <a title="Merge two or more arrays in PHP" href="http://php.net/array_merge" target="_blank">array_merge()</a> to do this in the past, it&#8217;s important to note the difference between <em>merging</em> arrays and <em>concatenating</em> them. When you merge they keys are used to determine how the resulting array is formed. When you concatenate the values are added together.</p>
]]></content:encoded>
			<wfw:commentRss>http://santiance.com/2009/08/tip-append-to-an-array-with/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tip: Don&#8217;t close your PHP tags</title>
		<link>http://santiance.com/2009/08/tip-dont-close-your-php-tags/</link>
		<comments>http://santiance.com/2009/08/tip-dont-close-your-php-tags/#comments</comments>
		<pubDate>Sat, 08 Aug 2009 12:32:05 +0000</pubDate>
		<dc:creator>Kristopher Ives</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Tip]]></category>

		<guid isPermaLink="false">http://67.43.13.30/~kives/wp/?p=49</guid>
		<description><![CDATA[Adding a closing ?&#62; to your &#60;?php tags is actually optional, and you should avoid using it for scripts that will only be included. I know a lot of you might be groaning and thinking &#8220;Just because you can, doesn&#8217;t mean you should&#8221;. We should always close our HTML tags and other things to avoid [...]]]></description>
			<content:encoded><![CDATA[<p>Adding a closing <code>?&gt;</code> to your <code>&lt;?php</code> tags is actually optional, and you should avoid using it for scripts that will only be included.</p>
<p><span id="more-49"></span></p>
<p>I know a lot of you might be groaning and thinking &#8220;Just because you can, doesn&#8217;t mean you should&#8221;. We should always close our HTML tags and other things to avoid quirks, but this is actually quite different. PHP doesn&#8217;t require or desire that you close them. However, the small savings you&#8217;ll get from not closing them isn&#8217;t the reason you should be avoiding them.</p>
<p>Closing them can cause you to accidentaly leave a whitespace or new-line character at the end of your scripts. These characters will cause the HTTP headers to be sent to the browser, which will make some other functions (such as <a title="Function that registers a session in PHP" href="http://php.net/session_start" target="_blank">session_start()</a>) that modify these headers to fail.</p>
]]></content:encoded>
			<wfw:commentRss>http://santiance.com/2009/08/tip-dont-close-your-php-tags/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
