Restrict the amount of CPU and memory resources that Chrome can consume.
Tested on Ubuntu 16.04/Linux Mint 18.
Install cgroups:
sudo apt install cgroup-bin
#!/bin/bash | |
# Sets each CUDA device to persistence mode and sets the application clock | |
# and power limit to the device's maximum supported values. | |
# When run with "--dry-run" as first command line argument or not as superuser, | |
# will display the commands, otherwise it will execute them. | |
# | |
# Hint: To run this at boot time, place this script in /root and create a file | |
# /etc/cron.d/nvidia_boost with the following single line: | |
# @reboot root /root/nvidia_boost.sh >/dev/null | |
# |
Restrict the amount of CPU and memory resources that Chrome can consume.
Tested on Ubuntu 16.04/Linux Mint 18.
Install cgroups:
sudo apt install cgroup-bin
Updated 4/11/2018
Here's my experience of installing the NVIDIA CUDA kit 9.0 on a fresh install of Ubuntu Desktop 16.04.4 LTS.
# On the host to run the container | |
docker run --privileged -i -t -v ~/host-folder-to-mount:/root/folder-ro:ro ubuntu | |
# Inside the container | |
# Need to create the upper and work dirs inside a tmpfs. | |
# Otherwise OverlayFS complains about AUFS folders. | |
mkdir -p /tmp/overlay && \ | |
mount -t tmpfs tmpfs /tmp/overlay && \ | |
mkdir -p /tmp/overlay/{upper,work} && \ | |
mkdir -p /root/folder && \ |
FROM php:5-apache | |
RUN apt-get update && \ | |
apt-get install -y \ | |
libc-client-dev libkrb5-dev && \ | |
rm -r /var/lib/apt/lists/* | |
RUN docker-php-ext-configure imap --with-kerberos --with-imap-ssl && \ | |
docker-php-ext-install -j$(nproc) imap |
git clone [email protected]:docker-library/php.git docker-library-php | |
## Go to the specific version you're interested in | |
cd docker-library-php/7.1/fpm/alpine | |
## Edit the .Dockerfile. | |
## Change | |
## ENV PHP_EXTRA_CONFIGURE_ARGS --enable-fpm --with-fpm-user=www-data --with-fpm-group=www-data | |
## to | |
## ENV PHP_EXTRA_CONFIGURE_ARGS --enable-fpm --with-fpm-user=www-data --with-fpm-group=www-data --enable-debug | |
## Comment out or delete: |
kubectl get pods | grep Evicted | awk '{print $1}' | xargs kubectl delete pod |
# The initial version | |
if [ ! -f .env ] | |
then | |
export $(cat .env | xargs) | |
fi | |
# My favorite from the comments. Thanks @richarddewit & others! | |
set -a && source .env && set +a |
This was tested on a ThinkPad P70 laptop with an Intel integrated graphics and an NVIDIA GPU:
lspci | egrep 'VGA|3D'
00:02.0 VGA compatible controller: Intel Corporation Device 191b (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GM204GLM [Quadro M3000M] (rev a1)
A reason to use the integrated graphics for display is if installing the NVIDIA drivers causes the display to stop working properly.
In my case, Ubuntu would get stuck in a login loop after installing the NVIDIA drivers.
This happened regardless if I installed the drivers from the "Additional Drivers" tab in "System Settings" or the ppa:graphics-drivers/ppa
in the command-line.