<?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: First week of Krita full-time hacking</title>
	<atom:link href="http://lukast.mediablog.sk/log/?feed=rss2&#038;p=163" rel="self" type="application/rss+xml" />
	<link>http://lukast.mediablog.sk/log/?p=163</link>
	<description>Just some notes about developing and using Linux</description>
	<lastBuildDate>Mon, 30 Aug 2010 19:48:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kevin Kofler</title>
		<link>http://lukast.mediablog.sk/log/?p=163&#038;cpage=1#comment-1891</link>
		<dc:creator>Kevin Kofler</dc:creator>
		<pubDate>Fri, 05 Feb 2010 15:31:16 +0000</pubDate>
		<guid isPermaLink="false">http://lukast.mediablog.sk/log/?p=163#comment-1891</guid>
		<description>Maybe approximating the atan with something else would be an option? E.g. use some integration formula on 1/(1+x²), or use a polynomial approximation.</description>
		<content:encoded><![CDATA[<p>Maybe approximating the atan with something else would be an option? E.g. use some integration formula on 1/(1+x²), or use a polynomial approximation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boudewijn Rempt</title>
		<link>http://lukast.mediablog.sk/log/?p=163&#038;cpage=1#comment-1859</link>
		<dc:creator>Boudewijn Rempt</dc:creator>
		<pubDate>Tue, 02 Feb 2010 15:43:05 +0000</pubDate>
		<guid isPermaLink="false">http://lukast.mediablog.sk/log/?p=163#comment-1859</guid>
		<description>My guess would be that to find hardware that works with OpenSolaris, installing it, making Lukas familiar with opensolaris, then learning dtrace could easily eat up a month or two, maybe three. Systemtap might be an option since Lukas is already using fedora. But I doubt that systemtap would help us more than valgrind at this stage. Maybe when we&#039;ve optimized the hell out of our algorithms, memory and cache usages and are faced with weird latencies or io issues.</description>
		<content:encoded><![CDATA[<p>My guess would be that to find hardware that works with OpenSolaris, installing it, making Lukas familiar with opensolaris, then learning dtrace could easily eat up a month or two, maybe three. Systemtap might be an option since Lukas is already using fedora. But I doubt that systemtap would help us more than valgrind at this stage. Maybe when we&#8217;ve optimized the hell out of our algorithms, memory and cache usages and are faced with weird latencies or io issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Markus</title>
		<link>http://lukast.mediablog.sk/log/?p=163&#038;cpage=1#comment-1856</link>
		<dc:creator>Markus</dc:creator>
		<pubDate>Tue, 02 Feb 2010 12:20:04 +0000</pubDate>
		<guid isPermaLink="false">http://lukast.mediablog.sk/log/?p=163#comment-1856</guid>
		<description>Wouldn&#039;t using OpenSolaris with DTrace be better for finding performance bottlenecks?</description>
		<content:encoded><![CDATA[<p>Wouldn&#8217;t using OpenSolaris with DTrace be better for finding performance bottlenecks?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LukasT</title>
		<link>http://lukast.mediablog.sk/log/?p=163&#038;cpage=1#comment-1855</link>
		<dc:creator>LukasT</dc:creator>
		<pubDate>Tue, 02 Feb 2010 08:44:32 +0000</pubDate>
		<guid isPermaLink="false">http://lukast.mediablog.sk/log/?p=163#comment-1855</guid>
		<description>@chickenpump: yes, we decided to do lookup table for atan2. Problem is that it accept two parameters so it will be 2D lookup table and quite big probably.
But we plan to add lazy initialization, so it maybe quite fast.</description>
		<content:encoded><![CDATA[<p>@chickenpump: yes, we decided to do lookup table for atan2. Problem is that it accept two parameters so it will be 2D lookup table and quite big probably.<br />
But we plan to add lazy initialization, so it maybe quite fast.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Hards</title>
		<link>http://lukast.mediablog.sk/log/?p=163&#038;cpage=1#comment-1853</link>
		<dc:creator>Brad Hards</dc:creator>
		<pubDate>Tue, 02 Feb 2010 07:41:03 +0000</pubDate>
		<guid isPermaLink="false">http://lukast.mediablog.sk/log/?p=163#comment-1853</guid>
		<description>It might be worth tracking which compiler version and compiler options you are using for this. Obviously that could make some difference, although I readily concede it may not be very much in the end.</description>
		<content:encoded><![CDATA[<p>It might be worth tracking which compiler version and compiler options you are using for this. Obviously that could make some difference, although I readily concede it may not be very much in the end.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chickenpump</title>
		<link>http://lukast.mediablog.sk/log/?p=163&#038;cpage=1#comment-1849</link>
		<dc:creator>chickenpump</dc:creator>
		<pubDate>Mon, 01 Feb 2010 23:40:44 +0000</pubDate>
		<guid isPermaLink="false">http://lukast.mediablog.sk/log/?p=163#comment-1849</guid>
		<description>Hi Lukas,

just a tipp for the speedup of the atan2 function:

in the old amiga/atari days we used precomputed memory maps , like x = sinus_array[y] , which should also be possible for arc-tan (split to sin/cos)

this give a huuuge speedup there.</description>
		<content:encoded><![CDATA[<p>Hi Lukas,</p>
<p>just a tipp for the speedup of the atan2 function:</p>
<p>in the old amiga/atari days we used precomputed memory maps , like x = sinus_array[y] , which should also be possible for arc-tan (split to sin/cos)</p>
<p>this give a huuuge speedup there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boudewijn Rempt</title>
		<link>http://lukast.mediablog.sk/log/?p=163&#038;cpage=1#comment-1843</link>
		<dc:creator>Boudewijn Rempt</dc:creator>
		<pubDate>Mon, 01 Feb 2010 15:28:38 +0000</pubDate>
		<guid isPermaLink="false">http://lukast.mediablog.sk/log/?p=163#comment-1843</guid>
		<description>Dmitry,

Wouldn&#039;t that only work for composite_copy or composite_over with 100% opacity? Or do you want to pass the compositeop object to the datamanager?</description>
		<content:encoded><![CDATA[<p>Dmitry,</p>
<p>Wouldn&#8217;t that only work for composite_copy or composite_over with 100% opacity? Or do you want to pass the compositeop object to the datamanager?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DmitryK</title>
		<link>http://lukast.mediablog.sk/log/?p=163&#038;cpage=1#comment-1837</link>
		<dc:creator>DmitryK</dc:creator>
		<pubDate>Mon, 01 Feb 2010 09:49:07 +0000</pubDate>
		<guid isPermaLink="false">http://lukast.mediablog.sk/log/?p=163#comment-1837</guid>
		<description>About iterators: iirc, KisRandomAccessor uses memmove for for storing cyclic cache instead of (i%N). I thing this is the easiest thing to fix =)
About bitBlt: we need to implement directBitBlt inside datamanager, that will be used when color spaces coincide. It will share the tiles directly. It should be really fast on tiles3.</description>
		<content:encoded><![CDATA[<p>About iterators: iirc, KisRandomAccessor uses memmove for for storing cyclic cache instead of (i%N). I thing this is the easiest thing to fix =)<br />
About bitBlt: we need to implement directBitBlt inside datamanager, that will be used when color spaces coincide. It will share the tiles directly. It should be really fast on tiles3.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
