aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorChocobozzz <me@florianbigard.com>2018-02-07 11:17:10 +0100
committerChocobozzz <me@florianbigard.com>2018-02-08 09:52:57 +0100
commit588d837c87074c2c866423a8594f6841143ee50b (patch)
tree61123cc2db500a46b84bd95cdbfb569634c69e94
parent9ccf111912cae2a345d8ca0cf412703e59d19cf8 (diff)
downloadPeerTube-588d837c87074c2c866423a8594f6841143ee50b.tar.gz
PeerTube-588d837c87074c2c866423a8594f6841143ee50b.tar.zst
PeerTube-588d837c87074c2c866423a8594f6841143ee50b.zip
Add note in FAQ for server hardware
-rw-r--r--FAQ.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/FAQ.md b/FAQ.md
index 1bcd6006a..ab565c59d 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -37,3 +37,16 @@ If you already have followers, you can't.
37 37
38If you don't have any followers, update your configuration and run 38If you don't have any followers, update your configuration and run
39`NODE_ENV=production npm run update-host` to update the torrent files (they contain your domain name). 39`NODE_ENV=production npm run update-host` to update the torrent files (they contain your domain name).
40
41
42## Should I have a big server to run PeerTube?
43
44Not really. For instance, the demonstration server [https://peertube.cpy.re](https://peertube.cpy.re) has 2 vCore and 2GB of RAM and consumes on average:
45 * **CPU** -> nginx ~ 20%, peertube ~ 10%, postgres ~ 1%, redis ~ 3%
46 * **RAM** -> nginx ~ 6MB, peertube ~ 120MB, postgres ~ 10MB, redis ~ 5MB
47
48So you would need:
49 * **CPU** 1 core if you don't enable transcoding, 2 at least if you enable it
50 * **RAM** 1GB
51 * **Storage** Completely depends on how many videos your users will upload
52