<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
This normally happens if the Wifi connection isn't fast / stable
enough for the WebSocket stream(s), or when the web server doesn't
get enough CPU share.<br>
<br>
It also depends on the frequency and volume of changes in the
metrics & logs, which need to be transported to the web
client(s).<br>
<br>
I had taken some measures to cut down the logging for these issues,
but I think that needs to be optimized further -- especially as logs
now also are transported to the web clients. If for example you've
got two web sessions open and the first runs into the overflow, the
second will be flooded with the warning messages and probably run
into overflow as well. I'll put that on my list.<br>
<br>
Steve, you can try raising the queue size, but I think you didn't
find the right queue. The default size is 50, the queue is created
in the WebSocketHandler constructor (m_jobqueue).<br>
<br>
If that helps we can raise it generally or add a config for this.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 11.01.21 um 11:15 schrieb Chris van
der Meijden:<br>
</div>
<blockquote type="cite"
cite="mid:1610360152.2251.4.camel@arachnon.de">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>Hi Steve</div>
<div><br>
</div>
<div>I know that one too.</div>
<div><br>
</div>
<div>Happens to me always, when I get CAN Errors when I wake up
the CAN 3 Bus on the VW e-Up.</div>
<div><br>
</div>
<div>Greetinx from Bavaria</div>
<div><br>
</div>
<div>Chris</div>
<div> </div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Am Montag, den 11.01.2021, 11:44 +0200 schrieb Steve Davies:</div>
<blockquote type="cite">
<div dir="ltr">Hi,
<div><br>
</div>
<div>I generally debug by watching the shell via the web
interface with logging from my vehicle module at debug or
verbose.</div>
<div><br>
</div>
<div>I seem to be hitting throughput limitations for the
websocket pushing the output to my client, though, and see
many of these:</div>
<div><br>
</div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div>log.20210110-144200:2021-01-10 14:17:39 SAST W
(1630612) websocket: WebSocketHandler[0x3f8531a4]: job
queue overflow resolved, 133 drops</div>
<div><br>
</div>
</blockquote>
<div>This especially happened when I went to a charger for a
test and was connected to the OVMS system on 192.168.4.1 on
the local Wifi AP that the OVMS creates.</div>
<div><br>
</div>
<div>Is this to be expected? Is it more efficient to "log
monitor" via ssh, or do I really need a serial connection
over USB?</div>
<div><br>
</div>
<div>I do see that the websocket overflows seem to occur when
any client is connected whether you are looking at the shell
or not. In my case I'm logging quite a lot and I guess I
exceed the 100 deep queue.</div>
<div><br>
</div>
I see that I can make the queue bigger for the websocket -
would it be a big problem to increase the 100 to 200 by
default?
<div><br>
</div>
<div>Thanks,</div>
<div>Steve</div>
<div><br>
</div>
</div>
<pre>_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
</body>
</html>