|
Size: 1149
Comment:
|
Size: 1695
Comment: Fix typo: backgroup -> background
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| ||Memory usage (RSS)||32 MB||48 MB|| | ||Memory usage (RSS)||32 MB||128 MB|| |
| Line 11: | Line 11: |
| ||File size||64MB||64MB|| | ||File size||256MB||256MB|| ||Background processes||2 ||5 || |
| Line 15: | Line 16: |
| The memory limit is based on Resident Set Size (RSS) memory by using Linux cgroups feature. You can actually use more than 32MB, but if you go over the limit your programs will be swapped out to disk and everything will run very slow. It's not advised to use 100% of the limit either, for the same reason as you would not run your desktop computer at 100% memory usage. You will get a warning if you use more than 80% of your memory limit when you log in. You can also show your current memory usage with the command `showmem` | The memory limit is based on [[Howto/ProcessManagement#Memory_usage|Resident Set Size (RSS)]] memory by using Linux cgroups feature. A free account can use 32 MB of RSS memory and a few MB swap. It's not a good idea to use 100% of the limit, for the same reason as you would not run your desktop computer at 100% memory usage. Keep below 80% memory usage to avoid warnings. If you get near the limit some programs will start to swap out, and everything will get very slow. If you hit the hard limit some of your processess will be killed according to the Linux OOM killer score. You can show your current memory usage with the command `showmem` == Background processes == Blinkenshell counts an end-user application like a background process, for example irssi or an email client. Helper utilities like screen, tmux, sshd or bash does not count towards to limit on background processes. For example, it's ok to run a screen with one irssi instance and one alpine instance on a free account. |
| Line 19: | Line 26: |
| * http://linux-mm.org/OOM_Killer |
Resource Limits
Blinkenshell has some limits on process and memory usage to make sure a single user does not bring down the entire machine. Some limits are higher on supporter accounts.
Type |
Free account limit |
Supporter account limit |
Memory usage (RSS) |
32 MB |
128 MB |
Addressable virtual memory |
256 MB |
256 MB |
Number of open files |
128 |
256 |
Number of processes |
25 |
50 |
SSH sessions |
6 |
6 |
File size |
256MB |
256MB |
Background processes |
2 |
5 |
Memory limit
The memory limit is based on Resident Set Size (RSS) memory by using Linux cgroups feature. A free account can use 32 MB of RSS memory and a few MB swap. It's not a good idea to use 100% of the limit, for the same reason as you would not run your desktop computer at 100% memory usage. Keep below 80% memory usage to avoid warnings. If you get near the limit some programs will start to swap out, and everything will get very slow. If you hit the hard limit some of your processess will be killed according to the Linux OOM killer score.
You can show your current memory usage with the command showmem
Background processes
Blinkenshell counts an end-user application like a background process, for example irssi or an email client. Helper utilities like screen, tmux, sshd or bash does not count towards to limit on background processes. For example, it's ok to run a screen with one irssi instance and one alpine instance on a free account.