>Apparently one of the worker threads runs the web interface when it is
accessed from a browser.
>another worker thread is assigned to the interface,
This is NOT possible!
Workers (1....X, 10000, 10001) are unable to provide the web interface.
The GUI (all functions) is provided by the MainThread only (also all STATS
connections and the SNMP stuff)!
This is shown in log - like:
Oct-16-17 08:19:27 [Main_Thread] Admin connection from user User on host
192.168.0.1:56642; page:/; session-ID:b281c59711d45544b0404004f4a11289;
Oct-16-17 08:19:33 [Main_Thread] Admin connection from user User on host
192.168.0.1:56643; page:/logout;
session-ID:51334d4b03a737f3f752510b11df9ff9;
Oct-16-17 08:19:33 [Main_Thread] Logout from admin interface requested for
user 'User' at '192.168.0.1'
Oct-16-17 08:19:33 [Main_Thread] Terminated WEB session
51334d4b03a737f3f752510b11df9ff9 for user 'User' at '192.168.0.1'
Oct-16-17 08:19:33 [Main_Thread] Terminated WEB session
b281c59711d45544b0404004f4a11289 for user 'User' at '192.168.0.1'
Oct-16-17 08:19:33 [Main_Thread] Terminated WEB session
244de1df0b3813999484b7bce6c70cfb for user 'User' at '192.168.0.1'
>Since there is no "logout" option,
The 'logout' buttons are in the GUI - both in the left menu, one at top,
the other at the bottom.
Keep in mind, that using the 'Connection Screen' and the 'Worker Status'
forces all workers to collect runtime data and to provide these data for
the MainThread.
This causes higher CPU and RAM usage and slows down the MainThread.
Thomas
Von: "James Moe" <ji...@sohnen-moe.com>
An: "ASSP development mailing list" <assp-test@lists.sourceforge.net>
Datum: 16.10.2017 00:00
Betreff: Re: [Assp-test] ASSP ramps up CPU usage after a time
On 10/02/2017 11:39 AM, James Moe wrote:
>
> opensuse v42.2
> linux v4.4.87-18.29-default x86_64
> assp v 2.5.5(17223)
> perl 5.18.2
>
> After some up time, usually in the range of 1 - 3 weeks, ASSP starts
> consuming considerably more CPU time.
>
Finally tracked down what is actually happening here.
Apparently one of the worker threads runs the web interface when it is
accessed from a browser. As soon as I logged into the interface the
usage went from 0.6% to 11% using Worker_1 thread.
If at some point I need to log in again (the browser closed erasing
all cookies), another worker thread is assigned to the interface,
increasing the CPU usage to 23%.
Since there is no "logout" option, I presume this would continue until
ASSP ran out of workers to handle the interface?
--
James Moe
moe dot james at sohnen-moe dot com
520.743.3936
Think.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
