This question already has answers here:
Limit chrome headless CPU and memory usage
(2 answers)
Many process of Google Chrome (32 bit)
(1 answer)
Closed 2 years ago.
I'm running C# Selenium.WebDriver.ChromeDriver v84.0.4147.3001 from .Net Core 3.1 WEB APPLICATION and Windows "MODIFIED MEMORY" do not stop increasing. When chromedriver.exe process reached 2.6 GB of Modified Memory other processes started crashing (full computer memory usage). "Regular" memory usage is OK, around 200 MB for chromedriver.
For chrome.exe was created 5 instances and memory usage was around 100 MB and 500 MB of modified memory total.
I'm running it in a Windows Server 2019 16gb + 8gb pagefile.
These are the ChromeDriver startup options:
--disable-gpu, --width=1920, --height=1080, --mute-audio, --no-sandbox, --disable-dev-shm-usage, --disable-breakpad
I tried with and without "--headless" mode. Normal mode is lighter.
I need to run multiple instances of chromewebdriver, but that way is impossible. Looks like Memory Leak, but I'm not sure.
Any ideas how to get around this problem?
Related
This question already has answers here:
OutOfMemoryError: insufficient memory in IntelliJ?
(2 answers)
Closed 1 year ago.
After installing PyCharm, I am getting this error
PyCharm (and all Jetbrains IDE's) use Java, and its memory usage can be configured with JVM Options
If you are trying to use IntelliJ/PyCharm on limited memory environments (like a Raspberry Pi), you'll need to reduce the memory size (-Xmx flag). Otherwise, use a lighter-weight option like VSCode or Jupyter for Python development
I've recently assembled a new AMD Desktop, to replace an older Dell Latitude E7540 laptop.
The AMD Desktop:
Ryzen 3 3100 # 3.8GHz (4C/8T), 32GB DDR4 3600 CL17 RAM, Corsair P600
Gen4 SSD
The DELL Laptop:
Dell Latitude E7540: Intel I7-5600U # 2.6GHz (2C/4T), 16 MB RAM DDR3 1600, Samsung mSATA PM851
On the new AMD Desktop, when executing a docker build command, two situations occur:
The performance is dreadful, even building a simple image, it takes a long time for the command to start. After starting, it takes a long long time to complete (when it completes)
The build window crashes almost 50% of the time.
The benchmarks indicate that the new AMD Desktop is 3.5x faster at single core, and 6x faster at multicore.
As such, I was expecting a much better performance with the new AMD Desktop.
Unfortunately, that's not the case, and for the same Dockerfile (which generates a very big image):
The Dell starts faster
The Dell completes faster (10m vs 30m)
On the Dell, the build window never crashes.
The only difference between both systems is that one is an Intel platform, the new one an Ryzen 3 AMD.
Environment Details are the same on both machines:
Windows Version: Windows 10 Ent. 19049
Docker Desktop Version: Docker 3.0.0
What can explain this abysmal performance on Docker-Desktop on the new AMD system?
After a few troubling days, i can confirm that the problem is not AMD related.
The culprit is the Antivirus, that when ON, its scanning the files used by Docker, which cause all the problems i've described.
Docker documentation states how to disable the antivirus to scan Docker related files:
https://docs.docker.com/engine/security/antivirus/
When antivirus software scans files used by Docker, these files may be locked in a way that causes Docker commands to hang.
One way to reduce these problems is to add the Docker data directory (/var/lib/docker on Linux, %ProgramData%\docker on Windows Server, or $HOME/Library/Containers/com.docker.docker/ on Mac) to the antivirus’s exclusion list. However, this comes with the trade-off that viruses or malware in Docker images, writable layers of containers, or volumes are not detected. If you do choose to exclude Docker’s data directory from background virus scanning, you may want to schedule a recurring task that stops Docker, scans the data directory, and restarts Docker.
VSCode Version: 1.20.1
OS Version: Windows 10 Home 64-bit
It has occured since a first-time clean installation. Every action (Input, selection, scrolling) has a small but very noticeable amount of lag (approx. 0.5s lag) every 10 or so seconds. This occurs on newly created empty files as well. CPU usage is normal (<5%) and RAM usage is normal (250mb).
PC Specs:
Intel Core i7-7700HQ 2.80GHz
8GB DDR4 RAM
Samsung 256GB SSD
(Nvidia GTX1060 GPU)
Does this issue occur when all extensions are disabled?: Yes
A production tomcat stopped responding after 8 hours of adding more cpu and ram during runtime. There is no traceable log in catalina.out.
java process was still running in the background. There is no load on the system during that time period. No sign of Out of memory.
apache-tomcat-7.0.55
tomcat-native-1.1.31
java version "1.8.0_66"
Red Hat Enterprise Linux Server release 6.6 (Santiago)
Could it be because of the cpu and ram upgrade? Thanks.
I saw a post about it for java 6. I am not sure it is related to my issue.
http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6840239
We have a Java EE application that runs in JBoss 7.1.1, and, we must run it in VirtualMachines (such as VMWare ESXI).
The thing is, when we run our app in the VM, the performance is dropped by 50% approx.
Seems like the GC goes crazy... as far I can tell, when GC runs, it take much more longer
than normal to "end", and block the application meanwhile.
Have anyone else had a experience like that? Any tips, tunning or a light that I can follow?
Thanks in advance.
EDIT
JVM has Xmx and Xms = 1Gb
VM has 4Gb RAM
Ubuntu Server 64
oracle JVM 64
I would say that before moving your app to VM with configuration you posted it was running on 32bit system and 32bit jvm and using same jvm parameters.
Trick is that you moved to 64bit with 64bit java but still assigned same amount of heap size for your application, what has happened in reality is that you app now has half the memory available that it used to have.
Every object on 64bit jvm is twice the size of the one of 32bit jvm.
Given configuration you have I would suggest few solutions:
increase heap size to 2G
or use compressed oops
or install 32bit jvm
Given that your application does not have more than 1.3G assigned it think best performance would be achieved by installing 32bit jvm and running with -Xms1300m -Xmx1300m.
You can go even step futher and have 32bit VM with 32bit linux installation.
64bit jvm is only useful if you need more than 1.3G of heap otherwise it just adds too much overhead.
Also you can run jvm with
-verbose:gc -XX:+PrintGCDetails
that will show you what is happening with GC, this can further help you tune your jvm.