# Distributed Transcoding/Scaling

**URL:** <https://forums.plex.tv/t/distributed-transcoding-scaling/76681>\
**Category:** Feature Suggestions\
**Created:** [September 17, 2014, 8:35am UTC](https://forums.plex.tv/t/distributed-transcoding-scaling/76681 "2014-09-17T08:35:47Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![flecom](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/flecom/32/5814_2.png) [@flecom](https://forums.plex.tv/u/flecom)\
**Post date:** [September 17, 2014, 8:35am UTC](https://forums.plex.tv/t/distributed-transcoding-scaling/76681/1 "2014-09-17T08:35:47Z")

</div>

I realize this is a longshot but right now my plex server is a quad socket system and it's barely keeping up with user load, looking at 8 socket systems and they are just astronomically expensive which got me thinking about the huge surplus of cheap dual socket blade servers

&nbsp;

what if there was a way of scaling plex itself to have separate compute/transcode nodes instead of just having one giant server...

&nbsp;

so for example, you have one box running plex itself, then several slaved boxes that simply get assigned transcode jobs from the master plex server?

&nbsp;

so

&nbsp;

Plex Server \>

&nbsp; Transcode Server 1

&nbsp; Transcode Server 2

&nbsp; Transcode Server 3

&nbsp;

etc as the first transcode server starts getting very busy (say \>75% CPU) start sending jobs to the second and so on until we run out of available transcode servers?

&nbsp;

like I said, I realize this is a long shot and maybe a handfull of users might even run into a scenario like this but it would definitely make plex a significantly more powerful platform for things like CCTV/MWTV replacement

&nbsp;

feel free to tell me I'm crazy :)

---

_[View the full topic](https://forums.plex.tv/t/distributed-transcoding-scaling/76681)._