<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>On 06/09/2023 20:26, Peter Bennett wrote:<br>
</p>
<blockquote type="cite"
cite="mid:90b28c28-1051-7ccc-b3ad-f3537bd4be49@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><br>
</p>
<div class="moz-cite-prefix">On 9/6/23 12:54, Jan Ceuleers wrote:<br>
</div>
<blockquote type="cite"
cite="mid:b52454f4-fd80-e6a4-76cf-1e0b4ce773aa@gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div class="moz-cite-prefix">On 03/09/2023 23:08, Peter Bennett
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:83e2d37e-130b-ad94-45e3-adc4fa03ba0d@gmail.com">Thanks
for testing this. I have about 1500 videos (on hard drive) and
it takes between 1 and 2 seconds. With 5500 videos I would
expect no more than 7 seconds. <br>
</blockquote>
<p>I just timed it again: it took 50 seconds.<br>
</p>
<blockquote type="cite"
cite="mid:83e2d37e-130b-ad94-45e3-adc4fa03ba0d@gmail.com">I
can investigate using a lazy load for videos. That may
conflict with the directory listing scheme I have, where
directories are listed and you can drill down. <br>
<br>
Do you use directories? <br>
</blockquote>
<p>I do use directories, yes. Lots of them:</p>
<ul>
<li>The top level is alphabetic in groups (0-9, A-B, C-D, E-F,
G-H, I-J, K-L, M, N-O-P-Q, R-S, T, U-V-W-X-Y-Z). So 12
directories at the top level.</li>
<li>The above directories contain movies, but also
subdirectories (for TV box sets).</li>
<li>The TV box set directories can contain subdirectories for
each season. Single-season series don't have these
subdirectories.<br>
</li>
</ul>
<blockquote type="cite"
cite="mid:83e2d37e-130b-ad94-45e3-adc4fa03ba0d@gmail.com">When
it takes a long time, how many rows are reported (at the top
level each direcory is a row)? <br>
</blockquote>
Not sure what you're asking. Is there an incantation I should
run to produce the answer?<br>
<blockquote type="cite"
cite="mid:83e2d37e-130b-ad94-45e3-adc4fa03ba0d@gmail.com"> <br>
Does clicking on a directory to see its contents also take a
long time? <br>
</blockquote>
No, that is instant.<br>
<blockquote type="cite"
cite="mid:83e2d37e-130b-ad94-45e3-adc4fa03ba0d@gmail.com"> <br>
Does clicking back on Videos at the top after looking at a
subdirectory also take a long time? <br>
</blockquote>
<p>No.</p>
<p>Many thanks, Jan<br>
</p>
<br>
</blockquote>
<p>Please try this, to see if the slowdown is on the backend:<br>
curl <a class="moz-txt-link-rfc2396E"
href="http://localhost:6544/Video/GetVideoList?Sort=FileName"
moz-do-not-send="true">"http://localhost:6544/Video/GetVideoList?Sort=FileName"</a>
>/dev/null</p>
<p>On my laptop it reports time spent 0:00:01 with over 7000
videos in my database.</p>
<p>If you are running your browser on a different computer from
the backend, then try from that computer:<br>
curl <a class="moz-txt-link-rfc2396E"
href="http://backend:6544/Video/GetVideoList?Sort=FileName"
moz-do-not-send="true">"http://backend:6544/Video/GetVideoList?Sort=FileName"</a>
>/dev/null</p>
<p>Look at the Time Spent. This will tell if it is a slowdown in
the network.</p>
<p>Peter</p>
<br>
</blockquote>
<p><br>
</p>
<p>You should also be able to use your browsers debug tools to see
how long each network operation takes as well.</p>
<p><br>
</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;">Big
disclosure I haven't been able to test the latest WebApp but when
Stuart and I started the initial development the WebApp was very
fast but as we added more stuff it started to slow down
dramatically for me but not for Stuart! I was seeing regular
delays of 10 to 15 seconds to update the screen. We never figured
out why I was seeing it and not Stuart or what the cause was.
Angular does shift most processing to the client end ie the
machine running the browser rather than what is more traditional
with stuff like php where most of the processing is done at the
server end. At the time I was using a 16 core Ryzen 7 so it can't
be lack of processing power on the client end. I was running the
BE in a ESXI virtual machine which may have contributed to the
slow down since the WebApp does sent many requests to the backends
services API but I never found any evidence to support that idea.</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;"><br>
</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;">If Jan is
seeing many of the screens showing very slow update times then she
may be seeing the same thing I was. If it's just one screen then
it's likely something else. One thing you need to know with
Angular is that it is basically one giant web page that has the
entire WebApp on it. Angular just hides and shows stuff based on
what the user clicks on once the page is loaded. It does mean that
the initial loading is always slow since the browser has to pull
the several hundred megabyte? of data for the entire WebApp before
it shows the page you want. At least that is the way I believe it
works. <br>
</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;"><br>
</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;"><br>
</p>
<p>Paul H.</p>
</body>
</html>