Note that there are some explanatory texts on larger screens.

plurals
  1. PORavenDB long response time for query, while was processed on server very fast
    primarykey
    data
    text
    <p>Raven.Server started and binded to port 8022. I initialize DataStore in the following way:</p> <pre><code> var store = new DocumentStore() { Url = "http://localhost:8022" }; store.Initialize(); </code></pre> <p>Then i'm making such query:</p> <pre><code> using (var session = store.OpenSession()) { Stopwatch watch = new Stopwatch(); watch.Start(); var result = session.LuceneQuery&lt;Item&gt;("Raven/DocumentsByEntityName") .WhereEquals("Tag", "Items") .ToList(); watch.Stop(); // watch.ElapsedMilliseconds == ~550 ms return result; } </code></pre> <p>And <code>watch.ElapsedMilliseconds</code> is always ~550 ms. But when i look to RavenDB console i see that query was processed in 3 ms:</p> <pre><code>Request # 170: GET - 3 ms - 200 - /indexes/Raven/DocumentsByEntityName?query=Tag%253A%255B%255BItems%255D%255D&amp;start=0&amp;pageSize=128 </code></pre> <p>Thus ~ 99.5% of time have been spent not in RavenDB. What is the problem? (RavenDB 147)</p> <p><strong>When i switch to self-hosting of RavenDB (i.e. as embedded client) everything is okay (~3ms).</strong></p> <p>To clarify that issue not in network, http debuggers, dns servers etc. i also tested this:</p> <pre><code> Stopwatch watch = new Stopwatch(); watch.Start(); WebClient client = new WebClient(); var result = client.DownloadString("http://127.0.0.1:8022/indexes/Raven/DocumentsByEntityName?query=Tag%253A%255B%255BItems%255D%255D&amp;start=0&amp;pageSize=128"); watch.Stop(); // watch.ElapsedMilliseconds == ~3-10ms </code></pre> <p>Fast. But switching to Raven.Client.Lightweight increase response time in 200 times (550-600 ms)</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload