Dear developers,<br><br>I&#39;m currently running the CVS head of Dec 11, 2008. I apologies in advance for missing on details. If needed I&#39;ll provide more. <br><br>Thank you, and<br>lots of wonderful wishes for Xmas and for the New Year!!!<br>
(this is the last email you&#39;ll get from me this year, I promise :))<br>l.<br><br>Observation 1:<br>When trying to run big numbers of clients simultaneously, the server crushes. For me it crushed with 70 and 100 clients fired at the same time.<br>
<br>Observation 2: <br>After running one query in a multi-user scenario (N clients/threads simultaneously) the memory footprint of mserver (% of the memory that the server occupies) grew. After repeating the experiment M times the memory grew each time with a constant. Running the same query sequentially the same number of times leaves the footprint of mserver constant. Could it be a faulty memory cleaning?<br>
<br>Query: q3.xq<br>let $col := fn:collection(&quot;MotiesTweedeKamer&quot;)<br>let $years := fn:distinct-values(<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for $date in $col//hiddendatum<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; return fn:substring(fn:string($date),1,4))<br>
for $y in $years<br>order by $y ascending<br>return &lt;result year=&quot;{$y}&quot; count=&quot;{<br>&nbsp;&nbsp;&nbsp; &nbsp;count($col//document[fn:substring(fn:string(.//hiddendatum),1,4) = $y])<br>}&quot;/&gt;<br><br>N=50 <br>M=1<br>$ perl runNclients.pl N=50<br>
$ top<br>PID USER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PR&nbsp; NI&nbsp; VIRT&nbsp; RES&nbsp; SHR S %CPU %MEM&nbsp;&nbsp;&nbsp; TIME+&nbsp; COMMAND&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>28563 lafanasi&nbsp; 20&nbsp;&nbsp; 0 6266m 5.1g 100m S&nbsp;&nbsp;&nbsp; 0 26.0&nbsp; 10:50.71 Mserver&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>M=2<br>PID USER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PR&nbsp; NI&nbsp; VIRT&nbsp; RES&nbsp; SHR S %CPU %MEM&nbsp;&nbsp;&nbsp; TIME+&nbsp; COMMAND&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
28563 lafanasi&nbsp; 20&nbsp;&nbsp; 0 7546m 5.9g 100m S&nbsp;&nbsp;&nbsp; 0 30.1&nbsp; 21:42.67 Mserver&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>...<br>N=60<br>M=10<br>PID USER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PR&nbsp; NI&nbsp; VIRT&nbsp; RES&nbsp; SHR S %CPU %MEM&nbsp;&nbsp;&nbsp; TIME+&nbsp; COMMAND&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>31182 lafanasi&nbsp; 20&nbsp;&nbsp; 0 17.3g 8.3g 100m S&nbsp;&nbsp;&nbsp; 0 42.3 263:45.37 Mserver&nbsp; <br>
...<br>M=30<br>PID USER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PR&nbsp; NI&nbsp; VIRT&nbsp; RES&nbsp; SHR S %CPU %MEM&nbsp;&nbsp;&nbsp; TIME+&nbsp; COMMAND&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>31182 lafanasi&nbsp; 20&nbsp;&nbsp; 0 22.7g 9.6g 100m S&nbsp;&nbsp;&nbsp; 0 48.8 395:08.87 Mserver&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br><br>Sequential run:<br><br>N=1<br>M=50 times <br>
PID USER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PR&nbsp; NI&nbsp; VIRT&nbsp; RES&nbsp; SHR S %CPU %MEM&nbsp;&nbsp;&nbsp; TIME+&nbsp; COMMAND&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>28372 lafanasi&nbsp; 20&nbsp;&nbsp; 0&nbsp; 839m 430m 100m S&nbsp;&nbsp;&nbsp; 1&nbsp; 2.1&nbsp;&nbsp; 6:26.65 Mserver&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br><br>M=100 times <br>PID USER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PR&nbsp; NI&nbsp; VIRT&nbsp; RES&nbsp; SHR S %CPU %MEM&nbsp;&nbsp;&nbsp; TIME+&nbsp; COMMAND&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
28372 lafanasi&nbsp; 20&nbsp;&nbsp; 0&nbsp; 839m 430m 100m S&nbsp;&nbsp;&nbsp; 1&nbsp; 2.1&nbsp;&nbsp; 6:26.65 Mserver&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br><br><br>Observation 3:<br>The times it takes to run 10 Tijah search queries simultaneously is the same as the time it takes to run them sequentially. The percentage of CPU used in both cases by mserver is also similar. Does tijah support multi-users? <br>
<br>Query: q2.xq<br>let $opt := &lt;TijahOptions ft-index=&quot;polietiekedata&quot; ir-model=&quot;NLLR&quot;/&gt;<br>let $c := collection(&quot;HAN&quot;)<br>let $qid :=&nbsp; tijah:query-id($c, &quot;//spreker[about(.,%KEYWORD%)]&quot;, $opt)<br>
for $res in tijah:nodes($qid)<br>return &lt;pair&gt;{( string($res/@naam), tijah:score($qid, $res))}&lt;/pair&gt;<br><br>20 users/threads<br>stopMserver,startMserver (to make sure that the server freed the memory)<br>$time Run20Threads(mclient -lx q2.xq)<br>
0.134u 0.118s 0:20.01 1.1%&nbsp;&nbsp;&nbsp; 0+0k 0+8io 0pf+0w<br><br>sequential run, 20 times<br>stopMserver, startMserver<br>$ time for i in `seq 1 10`; do mclient -lx q2.xq; done<br>0.060u 0.067s 0:19.74 0.6%&nbsp;&nbsp;&nbsp; 0+0k 0+8io 0pf+0w<br>
<br>Observation 4:<br>The mserver memory footprint grows very fast when running Tijah queries. When the footprint reaches 98% the query processing time gets really slow or the server crushes.<br><br>Query: the same as above<br>
<br>Sequential run, M=90 times<br>$stopMserver, startMserver<br>$for i in `seq 1 10`; do mclient -lx q2.xq; done<br>$ top<br>PID USER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PR&nbsp; NI&nbsp; VIRT&nbsp; RES&nbsp; SHR S %CPU %MEM&nbsp;&nbsp;&nbsp; TIME+&nbsp; COMMAND&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>24527 lafanasi&nbsp; 20&nbsp;&nbsp; 0 26.2g&nbsp; 19g&nbsp; 80m S&nbsp;&nbsp; 66 98.0&nbsp;&nbsp; 4:24.57 Mserver <br>
<br><br><br>