Mandrewoid

the way this is worded make sit sound like it's some big acheivement, like Linus has finally made it as a youtuber...

And.... WHAT HAPPENED TO NOT USING CLICKBAIT TITLES LINUS?
@nicklmg

@AlexTheGreatish

So my house is on a spring, and there's a pump in the basement that pumps  groundwater out and away from the house to prevent the basement flooding. 
It enters at about 5c, something like 100-300L/h depending on the time of year. I've been seriously considering for years now using this water to cool my PC. Since we're pumping it anyways, all I would have to do is divert it through my PC on the way out. 
 
Time for LMG to make a field trip I think

What about just caching the files on the editors' machines? Instead of having the cache be in a centralized location, each workstation would have its own cache and you would also have less network traffic. I am not sure if Windows supports this but there may be some third party software to do it. The idea would be that when you attempt to open a file in the cache directory, if it does not exist (or there is a mismatch of last-modified time stamp) then Windows (or whatever third party software) would stream in the file, in its entirety or maybe in certain sized chunks, to the cache, and meanwhile also serve it to the file handle that is trying to read. As for the "in its entirety" / "chunks" this would mean that there would not have to be an explicit request by the application to read a small region, in order to go ahead and also load what is likely to be read next anyway since it's nearby the requested region. Although I'm not sure if Windows / certain file APIs used by the application already try to pre-load more data themselves and buffer it in memory.

As I watched this video, a feeling crept on me that approaching this problem with a Windows Server solution is not guaranteed to have full control as you wish for. I'm a Linux server admin and creating a solution as you expressed in the video is pretty straight forward.
 
You set up your server with high speed low capacity and mechanical drives, for the sake of the argument two nvme SSDs of 1 TB each and 4 HDDs of 10 TB each (and a small SSD for the operating system). You create two file systems, ZFS or BtrFS, one of 2 TB on the nvme SSDs and one of 20 TB mirrored on the HDDs. Both file systems are opened to the network by Samba shares, one for "work flow" and one for archives.
Now you create an archiving / de-archiving script which handles the decision when to move projects around. Let's assume that every project begins with a folder with the projects name with all the files below it. I know that the project will be around 400 GB, but say they are a 10th of the size for this argument. 
We declare "enough space" as 25% or more left on the fast drives, so 500 GB or more free is "enough space". If the script runs once a day, during night time when probably no one edits? , this leaves with an example of 40 GB per project space for 12 new projects during the day before the script runs again.
 
First the script will perform an inventory. This is done by using the Linux file parameter "accessed time" (atime), which is updated every time a file is opened, whether or not is has been edited. First it scans the atime for the fast drives and creates an list of the projects ordered by atime: last accessed first, projects that hasn't been accessed frequently last. Along with this inventory the total project size is also archived. This list can become to look something like this (note that the first line is for explanation):
project atime size (GB)
PROJ1 2019-03-04 40,5
PROJ3 2019-03-04 39,3
PROJ2 2019-03-02 40,3
(and so on, you'll get the picture)
 
Secondly another archive list is created, of all the projects in the archive with the atime. If a project there is accessed, the script will note that this project is becoming "important" again, flagging it for move to the fast storage.
 
You can choose to leave the files on fast storage until you run out of space (say at 75% disk space used), or move a project by default to archive when it has not been accessed for a week. And move the project(s) from archive to fast when it has been accessed in the past day, keeping track of the disk space usage on the fast drives, potentially flagging the project with the oldest atime on fast storage to be moved to archive.
 
With a script like this you can be pretty versatile, building it completely to your liking. It is also possible to create "one network share" with both filesystems in it, keeping the user experience (as shown by Taran in the video) the least techy.
 
@LinusTech I am open to help exploring this possibility.

Well, it could have been Epyc...
...or you can just shell out ten grand to get one of those 1U Intel Ruler SSD storage server.

Der8auer had a lot of problems getting all 6 memory channels on his 28 core Xeon to work, even without dropping it. I think he said he mounted it like 10 times and eventually just went with 4 channels.
 
Perhaps the CPU is fine, and you're just having that problem?

Der8auer had a lot of problems getting all 6 memory channels on his 28 core Xeon to work, even without dropping it. I think he said he mounted it like 10 times and eventually just went with 4 channels.
 
Perhaps the CPU is fine, and you're just having that problem?

Der8auer had a lot of problems getting all 6 memory channels on his 28 core Xeon to work, even without dropping it. I think he said he mounted it like 10 times and eventually just went with 4 channels.
 
Perhaps the CPU is fine, and you're just having that problem?

The point of a "sleeper" is to surprise others in a public setting, like at a drag strip, with a "sleeper" car that embarrasses Hellcats or Demons, or a LAN party. Building a "sleeper" for your house is just putting new guts in an old case, nothing "sleeper" about that.

How I felt watching @3:20 Was really hoping James would show up with a monocle

What about a cheeseburger? 

Hm, what if you set up the PC in a vacuum chamber so you could drop the pressure enough to bring the boiling point of water down to, say, 50 C (but really I suppose you could use whatever you want), and then setup a hose to just drip one drop onto the heatsink every now and then, which would be removed by boiling it.

https://www.bigassfans.com
You're welcome.
 
^If you want static pressure

https://www.bigassfans.com
You're welcome.
 
^If you want static pressure

AWS is not cost-effective... We've looked into them for a few different ideas and always found that their pricing is obscene compared to alternatives. They're one of the most expensive options available as far as I know...
 
Don't get me wrong - they offer a ton of different services and their reliability is second to none from what I've heard, but for our purposes it really seems overkill.

 
We have a private offsite backup in a rack that's about 3 hrs away from the office by car.

Oh god, I hope not.  Plus, they'd ask for PHP devs if that were the case.
 
Wordpress is literally the last thing I'd use for something like this.  One would be better off using butterflies

I'm a software dev and founding member of 2 separate startups.  I'm gonna put my $0.02 Canadian Rubles in here and say that this is something that probably shouldn't be 100% in Node.  I know it simplifies things to have JS across the board, but hear me out.
 
Node will give you nothing but headaches when it comes to any real heavy lifting.
Video encoding?  Forget about it. 
Performance with huge amounts of concurrent users?  Only if you're willing to pay $$$ to Amazon for your d2.8xlarge instances
 
This is coming from someone who loves Node and JS in general.  I think this is something that will exist to only be re-written when any volume of users climb on.
 
I can hear it now. "Hey, asshole!  This is about iterating quickly, not optimization!".  I get that, and I know that quick iteration is crucial, but I'm going to propose what I think is a way better solution.
 
______________________________________________________________________________
 
You really should hire people to make an API in an appropriate language/framework. Choose Go, choose Django or Flask, hell, even choose Rails.  Don't choose JS.
 
Decoupling your API logic from your views allows for great flexibility in terms of tech used.  Node can be your presenter, while Go is running the business logic since that's what these languages excel at.  Then, when you want a desktop app, your Node project can be incorporated into Electron and still be served by that API.
 
Same with phone apps.  Use React Native as a presenter, use a stable API as your workhorse.
 
If you still need quick iteration, don't use Go and use Rails 5 API mode instead.  This way, you can start very quickly (much quicker than Node), then swap out services for an equivalent service in a better language when concurrency becomes an issue.  Websockets exist in pretty much every language/framework, so those are a non-issue.
 
_______________________________________________________________________________
 
Again, I'm a JS dev who also loves Rails and Go.  I think that Node is a very appealing choice for a lot of websites, but not one that requires real computational work to be done. 
 
 
 

1. I bet JFJ Jr wish he had floatplane
 
2. I make magic all the time.. I eat.. and it magically becomes plentiful poop
 
3. Boy, the code is going to get confusing.. you got couple of different types of Canadian English, English English and the Swedish Chef.

Deadline? Coders love deadlines.

PLEASE PLEASE PLEASE opensource parts of it to allow the whole community to contribute!
I normally hang around at the Level1Techs forums but made a account here just to stress that I would love to work on a node based high availability microservices video delivery infrastructure! And I think that there are a lot more people in the broader techtuber community who would contribute to something like this which is an exiting project and can help improve the infrastructure for content delivery and lessen the dependency on single corporations.
 
Exiting to see where this goes.

For future reference, I recommend selecting "auto" for your text color. This is how your post looks to dark theme users:
 

I got so triggered by that proprietary VGA cable