-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Occasional high CPU utilization of the ADC web browser tab https://127.0.0.1:5601/transfers and 2GB memory. #448
Comments
You should be using the latest application version |
Yes, I have updated per your suggestion. 😍 Running it around 2 days and the RAM is 150-350MB and CPU is 1-15%. After next 24 hours, usage is 450MB. |
I assume that the issue has then been fixed (I have no idea what could have caused it though) |
I am back, I do not see 100% CPU, but memory is back to 2GB after like 3 days of uptime, video of the Firefox "about:processes" page/tab is here. |
Daemon or browser (UI) uptime? The daemon won't matter here as the UI is effectively a separate application that runs in the browser. Can you test it with a different browser to see if it's the same? It would also good to know if the memory usage just steadily increases over time (maybe you could start with a fresh session and check the memory usage daily). |
Oh and will the memory usage remain reasonable if you don't open the transfers page? |
I was talking about system uptime, but anyway following is about ADC Client uptime: During 2GB RAM usage shown in Firefox, about:processes tab, the 127.0.0.1:5601/home shown that the Client started 4 days ago (i do not know if the process that is running inside browser has same age - i have seen some ADC UI crashes inside browser tab where page refresh instantly fix the ADC web client "crash". Then I have seen that the Firefox about:processes AirDC RAM usage dropped to 580MB, not 2GB as it was before. Firefox v. 102.11.0esr about:performance tab on other hand shows 40MB AirDC web client memory usage in LibreWolf and 21MB memory in Firefox.
Yes. I have closed the ADC client browser tab, restart ADC (actually kill it since i do not see shutdown button) and open ADC client browser tab on Search page and let it be 24 hours. RAM usage not raised and is around 100MB in Forefox. In LibreWolf browser it is 65MB even it was on Transfers tab... so the high mem. usage in displayed in FF seems to be caused by Transfers tab. |
40 MB under about:performance and 1GB under about:processes? You could also try "Free memory" functions under about:memory (GC/CC). The memory tab also has the "Measure" button under "Show memory reports" that might provide useful information. |
If you have browser extensions installed, it might be a good idea to have those disabled while testing |
yes. Here i paste "about:memory" -> Show memory reports -> Measure -> filter ADC port "5601" output during 359MB RAM usage (it risen from around 100MB since last like 9 hours when i have loaded Transfers tab): https://bin.disroot.org/?eba1202f01b644e4#J67pqAC1r1kX4TkskTTCm91zyYxXbPU2utu5QDuf9DB5 (password: adc) I have not disabled browser extensions.. |
I can see that there's something wrong with the list views as it keeps on fetching the same date over and over again. This only seems to happen with Firefox. |
Current UI and client versions:
Application version AirDC++w 2.11.2 x86_64
Web UI version 2.11.2
Web UI construir date September 19, 2021 10:12 AM
API version 1
API feature level 7
Started a day ago
Active sessions 1
Server threads 4
Operating system:
Debian 11 stable version of the distribution and also of the firefox-esr package (102.10.0esr (64-bit)) and KDE desktop.
Steps to reproduce the issue:
I usually have around ~7 active transfers each like 150kB/s.
Incoming searches (Total searches 3375455 (36.9 per second))
Average matching time per text search 28 ms
In mentioned Firefox-ESR, open on a new tab address "about:processes" and sort by CPU column.
Switch to Transfers tab https://127.0.0.1:5601/transfers and ideally make sure you have similar number of active transfers as me.
Switch back to "about:processes" tab (Firefox process manager) to see CPU usage of the Air DC, it is shown in 2 rows. In my case it sometimes spike to even 100%. and the memory figure of the AirDC tab is 2GB which is top memory hog of all open tabs, Next biggest is Twitter with 0.6GB (size of old operating system, which is still too much).
If you can think about some optimizations in this regard.
The text was updated successfully, but these errors were encountered: