Recommended hardware requirements for a big instance to handle 1,000 concurrent viewers (see our <a target="_blank" rel="noopener noreferrer" href="https://joinpeertube.org/news/stress-test-2023">blog post about our viewers stress test</a>):
Communicate with the streamer and other viewers using the <a target="_blank" rel="noopener noreferrer" href="https://livingston.frama.io/peertube-plugin-livechat/">livechat PeerTube plugin</a>
<a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/use/create-upload-video#upload-a-new-version-of-a-video">Upload a new version of the video</a> if your administrator enabled this setting
Communicate with your viewers using the <a target="_blank" rel="noopener noreferrer" href="https://livingston.frama.io/peertube-plugin-livechat/">livechat PeerTube plugin</a>
Video transcoding: can be mitigated using <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/admin/remote-runners">remote transcoding</a> by remote workers
Transcoding can also be offloaded to other machines using <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/admin/remote-runners">remote runners</a>.
But some pars of PeerTube can be horizontally scaled to bypass the following limits, as described in our <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/maintain/configuration#scalability">scalability guide</a>:
