﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Adam Langley commented on The RavenDB indexing process: Optimization&amp;ndash;De-parallelizing work</title><description>The wonderful thing about that scenario, is if the region of code you are optimising is modular (which I'm sure it is), the problem space is not variable once the software is installed.
Hence, you could provide two indexing modules, one designed for single-core, and one for multi-core parallelism.

Of course you would increase your code maintenance, but thats just another decision...</description><link>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment11</link><guid>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment11</guid><pubDate>Sun, 22 Apr 2012 21:00:26 GMT</pubDate></item><item><title>Ayende Rahien commented on The RavenDB indexing process: Optimization&amp;ndash;De-parallelizing work</title><description>Frank,
No, we didn't do that. We handle the control in a much simple concept by partitioning the work before starting the parallel work</description><link>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment10</link><guid>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment10</guid><pubDate>Sat, 21 Apr 2012 10:57:53 GMT</pubDate></item><item><title>Frank Quednau commented on The RavenDB indexing process: Optimization&amp;ndash;De-parallelizing work</title><description>Have you implemented your own Task Scheduler for the Task library?</description><link>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment9</link><guid>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment9</guid><pubDate>Sat, 21 Apr 2012 10:53:03 GMT</pubDate></item><item><title>Rafal commented on The RavenDB indexing process: Optimization&amp;ndash;De-parallelizing work</title><description>A nice thing about indexing in Raven is that usually you have all recently modified documents in memory so you can index them without reading from the storage. You will not have such luxury when the lucene index is external to the application</description><link>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment8</link><guid>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment8</guid><pubDate>Sat, 21 Apr 2012 10:37:21 GMT</pubDate></item><item><title>Ayende Rahien commented on The RavenDB indexing process: Optimization&amp;ndash;De-parallelizing work</title><description>Madhav,
RavenDB is DivanDB</description><link>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment7</link><guid>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment7</guid><pubDate>Sat, 21 Apr 2012 08:18:09 GMT</pubDate></item><item><title>Ayende Rahien commented on The RavenDB indexing process: Optimization&amp;ndash;De-parallelizing work</title><description>Matthew,
It is using a lot of CPU for full text indexing, it requires a lot of memory and it writes a lot to disk.
It wouldn't be workable to do this on the cloud, because the cost of actually sending the data up there and then getting it back would be too high.</description><link>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment6</link><guid>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment6</guid><pubDate>Sat, 21 Apr 2012 08:17:57 GMT</pubDate></item><item><title>Matthew Sullivan commented on The RavenDB indexing process: Optimization&amp;ndash;De-parallelizing work</title><description>Sorry if this question is too naive, but is the indexing primarily cpu bound, memory bound or i/o bound?  Would it be helpful or possible to use a cloud computing to create indexes in a speedy fashion?  

I've just heard that slow indexing speed is a major drawback of doc dbs, a prime reason why reporting etc needs to be done on sql... just wondering if you can throw a little cloud money at the problem to get faster turnaround on ad hoc reporting or index fixes.  </description><link>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment4</link><guid>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment4</guid><pubDate>Fri, 20 Apr 2012 17:20:10 GMT</pubDate></item><item><title>Gene Hughson commented on The RavenDB indexing process: Optimization&amp;ndash;De-parallelizing work</title><description>Performance tuning on a line of business app is expensive and labor-intensive to get right: you really need a comprehensive suite of load tests on the same hardware profile as production using an equivalent network profile - easy-peasy.  I can only imagine the headache involved with a more general-purpose tool like Raven.  Like Daniel above, I'm enjoying the peek into your world.</description><link>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment3</link><guid>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment3</guid><pubDate>Fri, 20 Apr 2012 14:25:07 GMT</pubDate></item><item><title>Daniel O commented on The RavenDB indexing process: Optimization&amp;ndash;De-parallelizing work</title><description>Enjoying these posts on the ongoing development of RavenDB. Could you imagine if the SQL Server or Oracle devs did posts like this?</description><link>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment2</link><guid>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment2</guid><pubDate>Fri, 20 Apr 2012 12:47:18 GMT</pubDate></item><item><title>gandjustas commented on The RavenDB indexing process: Optimization&amp;ndash;De-parallelizing work</title><description>What actual API you used for parallel computations? 
Parallel.ForEach? It's not suitable for IO-bound concurrency. 
For IO-bound you should use Tasks.</description><link>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment1</link><guid>http://ayende.com/155393/the-ravendb-indexing-process-optimization-de-parallelizing-work#comment1</guid><pubDate>Fri, 20 Apr 2012 09:27:25 GMT</pubDate></item></channel></rss>