<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	
	>
<channel>
	<title>Comments on: Computer Algorithms: Jump Search</title>
	<atom:link href="/2011/12/12/computer-algorithms-jump-search/feed/" rel="self" type="application/rss+xml" />
	<link>/2011/12/12/computer-algorithms-jump-search/</link>
	<description>on web development</description>
	<lastBuildDate>Fri, 26 Oct 2018 21:40:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.0.3</generator>
	<item>
		<title>By: Nikolay Mihaylov</title>
		<link>/2011/12/12/computer-algorithms-jump-search/comment-page-1/#comment-414240</link>
		<dc:creator><![CDATA[Nikolay Mihaylov]]></dc:creator>
		<pubDate>Fri, 22 Jul 2016 18:38:25 +0000</pubDate>
		<guid isPermaLink="false">/?p=2521#comment-414240</guid>
		<description><![CDATA[I am currently programming binary search in disk file. I found out that jump search will be better suited, because the OS will cache the jump &quot;points&quot; and jumps will be at no additional &quot;cost&quot;.

Sure this is true for dividing &quot;points&quot; of the binary search too, but they have how to say &quot;priority&quot; (central element is the most used) and OS cache do not perform that well.

Rudimentary benchmark show if bin search doing it for 40 - 50 sec every time, jump search (after first 3-4 searches) is doing it for 3-4 sec.]]></description>
		<content:encoded><![CDATA[<p>I am currently programming binary search in disk file. I found out that jump search will be better suited, because the OS will cache the jump &#8220;points&#8221; and jumps will be at no additional &#8220;cost&#8221;.</p>
<p>Sure this is true for dividing &#8220;points&#8221; of the binary search too, but they have how to say &#8220;priority&#8221; (central element is the most used) and OS cache do not perform that well.</p>
<p>Rudimentary benchmark show if bin search doing it for 40 &#8211; 50 sec every time, jump search (after first 3-4 searches) is doing it for 3-4 sec.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stoimen</title>
		<link>/2011/12/12/computer-algorithms-jump-search/comment-page-1/#comment-14860</link>
		<dc:creator><![CDATA[Stoimen]]></dc:creator>
		<pubDate>Tue, 13 Dec 2011 10:10:28 +0000</pubDate>
		<guid isPermaLink="false">/?p=2521#comment-14860</guid>
		<description><![CDATA[@Jordan Harband - thanks for the remark! fixed!]]></description>
		<content:encoded><![CDATA[<p>@Jordan Harband &#8211; thanks for the remark! fixed!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan Harband</title>
		<link>/2011/12/12/computer-algorithms-jump-search/comment-page-1/#comment-14847</link>
		<dc:creator><![CDATA[Jordan Harband]]></dc:creator>
		<pubDate>Mon, 12 Dec 2011 18:35:59 +0000</pubDate>
		<guid isPermaLink="false">/?p=2521#comment-14847</guid>
		<description><![CDATA[In your PHP jump search implementation, the line &quot;$step += $step;&quot; means that the step will go from √n -&#062; 2√n -&#062; 4√n -&#062; 8√n, when you want it to go from √n -&#062; 2√n -&#062; 3√n -&#062; 4√n.

You either need a coefficient variable that gets increased by 1 (ie, $step_iteration = $coefficient * $step) or you need a separate $step_iteration variable (ie, $step should never be modified, and each iteration, $step_iteration += $step).]]></description>
		<content:encoded><![CDATA[<p>In your PHP jump search implementation, the line &#8220;$step += $step;&#8221; means that the step will go from √n -&gt; 2√n -&gt; 4√n -&gt; 8√n, when you want it to go from √n -&gt; 2√n -&gt; 3√n -&gt; 4√n.</p>
<p>You either need a coefficient variable that gets increased by 1 (ie, $step_iteration = $coefficient * $step) or you need a separate $step_iteration variable (ie, $step should never be modified, and each iteration, $step_iteration += $step).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
