﻿<?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>Chris Eldredge commented on NuGet Perf, The Final Part &amp;ndash; Load Testing &amp;ndash; Results ^ 2</title><description>Reviewing the test plan it seems only 6 search terms are used: orm, nhibernate, yui, grid, debug, ravendb. My analysis shows there are over 3,400 unique terms in the Tags field, 6,500 in ReleaseNotes and 9,000 in Description.

No phrase queries, no variation in sort order and only 6 term queries does not seem like an adequate simulation of the types of queries that nuget.org is likely to experience in high volume.

With such a small number of unique queries, the server can simply return cached results without experiencing virtually any memory pressure or CPU spikes.

Since no packages are being added to the index nor are download counters being incremented, the data store is effectively in read-only mode, making the simulation even less accurate in comparison to real traffic.

With all of those considerations, I don't think this load test fairly compares RavenDB to the SQL Server/EF solution in use on nuget.org.</description><link>http://ayende.com/158593/nuget-perf-the-final-part-load-testing-results-2#comment3</link><guid>http://ayende.com/158593/nuget-perf-the-final-part-load-testing-results-2#comment3</guid><pubDate>Tue, 18 Sep 2012 16:37:59 GMT</pubDate></item><item><title>adam commented on NuGet Perf, The Final Part &amp;ndash; Load Testing &amp;ndash; Results ^ 2</title><description>Too bad ravendb can't serve odata or this would be a no-brainer for the nuget team to implement.

This is a great series of posts.  I think this clearly demonstrates how a traditional rdbms is not designed to handle the average use case of today's applications.  Yes, you could optimize the heck out of your model and db to try and make it perform but the out of the box experience of ravendb just works, and works well.  Even with an optimized rdbms things like search are always going to perform poorly just because they are not designed for this use case.  A rdbms still has its place, but its not for the traditional web app anymore.
</description><link>http://ayende.com/158593/nuget-perf-the-final-part-load-testing-results-2#comment2</link><guid>http://ayende.com/158593/nuget-perf-the-final-part-load-testing-results-2#comment2</guid><pubDate>Mon, 17 Sep 2012 14:54:20 GMT</pubDate></item><item><title>njy commented on NuGet Perf, The Final Part &amp;ndash; Load Testing &amp;ndash; Results ^ 2</title><description>These numbers are so great that i would like to see what would came out of a production environment with an even higher number of users like... i mean... vulgar display of power :)</description><link>http://ayende.com/158593/nuget-perf-the-final-part-load-testing-results-2#comment1</link><guid>http://ayende.com/158593/nuget-perf-the-final-part-load-testing-results-2#comment1</guid><pubDate>Mon, 17 Sep 2012 14:19:34 GMT</pubDate></item></channel></rss>