﻿<?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>Ayende Rahien commented on RavenDB indexing optimizations, Step III&amp;ndash;Skipping the disk altogether</title><description>PS,
Exactly the reason why we have the previous two options. This is an optimization only, it does NOT impact how operations.
Feel free to turn off the plug at any time, it will work.</description><link>http://ayende.com/160291/ravendb-indexing-optimizations-step-iii-skipping-the-disk-altogether#comment5</link><guid>http://ayende.com/160291/ravendb-indexing-optimizations-step-iii-skipping-the-disk-altogether#comment5</guid><pubDate>Sun, 16 Dec 2012 17:47:30 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB indexing optimizations, Step III&amp;ndash;Skipping the disk altogether</title><description>Theo,
I recommend using the latest, but they came throughout the RavenDB 2.0 pipeline.</description><link>http://ayende.com/160291/ravendb-indexing-optimizations-step-iii-skipping-the-disk-altogether#comment4</link><guid>http://ayende.com/160291/ravendb-indexing-optimizations-step-iii-skipping-the-disk-altogether#comment4</guid><pubDate>Sun, 16 Dec 2012 17:46:40 GMT</pubDate></item><item><title>Rangoric commented on RavenDB indexing optimizations, Step III&amp;ndash;Skipping the disk altogether</title><description>@PS those documents are also written to disk while/before being indexed. It's just that when the documents come in, they being being sent straight to the index queue instead of being written, then read back off the disk, then put in the index queue.

If there was a power outage, a document might be indexed, but I'm pretty sure the start up clean up would handle that case because IIRC when it starts up it checks when it was working on to see what finished and goes from there on a bad shut down.</description><link>http://ayende.com/160291/ravendb-indexing-optimizations-step-iii-skipping-the-disk-altogether#comment3</link><guid>http://ayende.com/160291/ravendb-indexing-optimizations-step-iii-skipping-the-disk-altogether#comment3</guid><pubDate>Fri, 14 Dec 2012 14:02:50 GMT</pubDate></item><item><title>PS commented on RavenDB indexing optimizations, Step III&amp;ndash;Skipping the disk altogether</title><description>what if there is a power outage during indexing of documents in memory (not yet written to disk). Can you thus run into an issue where there is a document indexed, but got lost during the outage before it got a chance to get written to disk?</description><link>http://ayende.com/160291/ravendb-indexing-optimizations-step-iii-skipping-the-disk-altogether#comment2</link><guid>http://ayende.com/160291/ravendb-indexing-optimizations-step-iii-skipping-the-disk-altogether#comment2</guid><pubDate>Fri, 14 Dec 2012 12:56:59 GMT</pubDate></item><item><title>Theo commented on RavenDB indexing optimizations, Step III&amp;ndash;Skipping the disk altogether</title><description>Interesting

In which build are these indexing optimizations available?</description><link>http://ayende.com/160291/ravendb-indexing-optimizations-step-iii-skipping-the-disk-altogether#comment1</link><guid>http://ayende.com/160291/ravendb-indexing-optimizations-step-iii-skipping-the-disk-altogether#comment1</guid><pubDate>Fri, 14 Dec 2012 10:26:31 GMT</pubDate></item></channel></rss>