<?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: db4o Performance Pitfalls</title>
	<atom:link href="http://www.emphess.net/2010/02/11/db4o-performance-pitfalls/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.emphess.net/2010/02/11/db4o-performance-pitfalls/</link>
	<description>Christoph Menge&#039;s Blog</description>
	<lastBuildDate>Tue, 15 Jun 2010 00:52:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Christoph Menge</title>
		<link>http://www.emphess.net/2010/02/11/db4o-performance-pitfalls/comment-page-1/#comment-1966</link>
		<dc:creator>Christoph Menge</dc:creator>
		<pubDate>Sun, 14 Mar 2010 17:49:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.emphess.net/?p=96#comment-1966</guid>
		<description>In my case, yes. Native query optimization in db4o depends on those dlls - if the .dlls are missing, optimization won&#039;t work.

However, there are many reasons why the optimization could still fail. Mostly this happens because people call methods that can&#039;t be optimized. 

The current optimizer supports only a small subset of what LINQ to objects supports. Complicated string operations won&#039;t be optimized either. See http://developer.db4o.com/Documentation/Reference/db4o-7.12/net35/reference/html/reference/tuning/native_query_optimization.html for details and a list of supported operations.</description>
		<content:encoded><![CDATA[<p>In my case, yes. Native query optimization in db4o depends on those dlls &#8211; if the .dlls are missing, optimization won&#8217;t work.</p>
<p>However, there are many reasons why the optimization could still fail. Mostly this happens because people call methods that can&#8217;t be optimized. </p>
<p>The current optimizer supports only a small subset of what LINQ to objects supports. Complicated string operations won&#8217;t be optimized either. See <a href="http://developer.db4o.com/Documentation/Reference/db4o-7.12/net35/reference/html/reference/tuning/native_query_optimization.html" rel="nofollow">http://developer.db4o.com/Documentation/Reference/db4o-7.12/net35/reference/html/reference/tuning/native_query_optimization.html</a> for details and a list of supported operations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benny</title>
		<link>http://www.emphess.net/2010/02/11/db4o-performance-pitfalls/comment-page-1/#comment-1965</link>
		<dc:creator>Benny</dc:creator>
		<pubDate>Sun, 14 Mar 2010 17:39:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.emphess.net/?p=96#comment-1965</guid>
		<description>For this optimizer to work, just put those dll? no code change required?</description>
		<content:encoded><![CDATA[<p>For this optimizer to work, just put those dll? no code change required?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: siaqodb_user</title>
		<link>http://www.emphess.net/2010/02/11/db4o-performance-pitfalls/comment-page-1/#comment-1945</link>
		<dc:creator>siaqodb_user</dc:creator>
		<pubDate>Sun, 28 Feb 2010 23:13:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.emphess.net/?p=96#comment-1945</guid>
		<description>Christoph,
Indeed siaqodb is commercial, but as you said: &quot;On the other hand, for a commercial project I’d stick to a solution that has some history and a strong community.&quot; this means you need also to buy license for db4o because for commercial projects db4o is not free.
Is also true that siaqodb is not lauched too long time ago, but already has a lot of interests from developers and speacially from Silverlight developers because LINQ is supported by siaqodb on Silverlight and has small footprint which is very important because user need to download small .XAP file.</description>
		<content:encoded><![CDATA[<p>Christoph,<br />
Indeed siaqodb is commercial, but as you said: &#8220;On the other hand, for a commercial project I’d stick to a solution that has some history and a strong community.&#8221; this means you need also to buy license for db4o because for commercial projects db4o is not free.<br />
Is also true that siaqodb is not lauched too long time ago, but already has a lot of interests from developers and speacially from Silverlight developers because LINQ is supported by siaqodb on Silverlight and has small footprint which is very important because user need to download small .XAP file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christoph Menge</title>
		<link>http://www.emphess.net/2010/02/11/db4o-performance-pitfalls/comment-page-1/#comment-1944</link>
		<dc:creator>Christoph Menge</dc:creator>
		<pubDate>Fri, 26 Feb 2010 14:38:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.emphess.net/?p=96#comment-1944</guid>
		<description>Thanks for the comment. I think it&#039;s good to see more innovative solutions approaching data storage come up. 

What I posted is not entirely specific to db4o: calling a lambda expression will require object instantiation, while parsing the expression tree does not. The latter is obviously much faster, but also more complicated. db4o&#039;s support for it is quite good, however - as long as you don&#039;t leave out the required libraries.

siaqodb sure looks interesting because it has a very small footprint. On the other hand, for a commercial project I&#039;d stick to a solution that has some history and a strong community.

Also, siaqodb is not open source which would help to build the required amount of trust, especially in the beginning where community support will not be strong.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment. I think it&#8217;s good to see more innovative solutions approaching data storage come up. </p>
<p>What I posted is not entirely specific to db4o: calling a lambda expression will require object instantiation, while parsing the expression tree does not. The latter is obviously much faster, but also more complicated. db4o&#8217;s support for it is quite good, however &#8211; as long as you don&#8217;t leave out the required libraries.</p>
<p>siaqodb sure looks interesting because it has a very small footprint. On the other hand, for a commercial project I&#8217;d stick to a solution that has some history and a strong community.</p>
<p>Also, siaqodb is not open source which would help to build the required amount of trust, especially in the beginning where community support will not be strong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: siaqodb_user</title>
		<link>http://www.emphess.net/2010/02/11/db4o-performance-pitfalls/comment-page-1/#comment-1943</link>
		<dc:creator>siaqodb_user</dc:creator>
		<pubDate>Thu, 25 Feb 2010 20:50:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.emphess.net/?p=96#comment-1943</guid>
		<description>You can also try siaqodb ( http://siaqodb.com ). Has also very fast LINQ queries and in plus support LINQ on Silverlight</description>
		<content:encoded><![CDATA[<p>You can also try siaqodb ( <a href="http://siaqodb.com" rel="nofollow">http://siaqodb.com</a> ). Has also very fast LINQ queries and in plus support LINQ on Silverlight</p>
]]></content:encoded>
	</item>
</channel>
</rss>
