WEBVTT 00:00:00.080 --> 00:00:06.960 that right there is a 512 00:00:04.880 --> 00:00:11.360 Gigabyte dim inside this box 00:00:09.360 --> 00:00:14.480 is a server with somewhere in the neighborhood 00:00:12.559 --> 00:00:19.199 of three to six terabytes of memory 00:00:16.640 --> 00:00:24.160 sort of this gives it the capability to run workloads like simulations with 00:00:21.840 --> 00:00:29.359 never-before-seen complexity without suffering large performance penalties 00:00:26.160 --> 00:00:30.560 for swapping data in and out of its bulk 00:00:29.359 --> 00:00:35.200 storage mostly now they're really savvy among 00:00:32.480 --> 00:00:39.920 you probably already have an idea of what's in here but for everyone else 00:00:38.480 --> 00:00:45.360 let me tell you something what if i said that you could take an 00:00:42.559 --> 00:00:49.680 SSD and put it right into your system memory slot instead of RAM 00:00:57.360 --> 00:01:03.039 today's video is brought to you by pulseway those guys are always all over 00:01:00.640 --> 00:01:06.799 our server content and why not pulseway is a great way to remotely manage your 00:01:04.799 --> 00:01:10.240 servers and other it infrastructure check them out at the link below to 00:01:08.400 --> 00:01:14.000 learn more now i'm not really expecting this thing 00:01:12.400 --> 00:01:20.080 to look unusual but 00:01:16.240 --> 00:01:23.040 it is a very very unusual 00:01:20.080 --> 00:01:23.040 accessory kit 00:01:23.680 --> 00:01:30.960 whatever this is what the hell is this 00:01:28.880 --> 00:01:36.159 on the one end it looks like a little tiny pci express six pin and on the 00:01:33.759 --> 00:01:38.840 other end it looks like a little tiny zeta connector 00:01:37.600 --> 00:01:44.000 what the heck it's labeled odd so optical drive 00:01:42.479 --> 00:01:47.040 what does this thing have an optical drive you're gonna be kidding me 00:01:47.520 --> 00:01:51.920 oh wow it's a skinny boy 00:01:52.479 --> 00:02:00.960 it's a 1u so this is a super slim server designed to be rack mounted with very 00:01:58.079 --> 00:02:04.399 high densities oh it's heavier than it looks uh one second 00:02:03.119 --> 00:02:12.239 all right is there anything else important in here let's go with no sweet ah 00:02:11.120 --> 00:02:17.599 okay oh somebody voided the warranty before i 00:02:15.360 --> 00:02:22.319 got to it you know i was wondering why it comes with a safety data sheet and a 00:02:19.599 --> 00:02:27.040 big warning label on the side turns out it's got a lithium battery 00:02:24.720 --> 00:02:30.480 a cr whatever you know one of those little button cells for making sure the 00:02:28.959 --> 00:02:34.000 BIOS doesn't lose its data while the system is powered off 00:02:32.000 --> 00:02:38.080 naturally a server has a very different port configuration compared to a desktop 00:02:36.080 --> 00:02:41.280 or a workstation so back here we've got a couple pci express slots what looks 00:02:40.000 --> 00:02:46.720 like some kind of mezzanine car will have to pop it open three usb 3s that's 00:02:44.400 --> 00:02:51.200 it and then four network ports one of which is for management so you can 00:02:48.560 --> 00:02:54.720 actually perform BIOS updates install operating systems all that kind of low 00:02:53.519 --> 00:02:59.120 level stuff monitor temperatures and fans and all 00:02:56.959 --> 00:03:02.239 that good stuff over the network rather than being plugged in directly if you do 00:03:00.480 --> 00:03:07.760 need to plug in directly of course it's got vga out so you can get that graphics 00:03:06.080 --> 00:03:11.280 you know connection on there 00:03:09.760 --> 00:03:14.480 for storage what are we looking at here oh wow 00:03:13.120 --> 00:03:19.519 oh they went and they put some good stuff in here neat 00:03:17.360 --> 00:03:25.440 well we've got at least two of Intel's dc p46 10 NVMe ssds 00:03:23.200 --> 00:03:30.239 so that's cool that answers my question as to whether 00:03:27.360 --> 00:03:34.400 these were NVMe or SATA base more envy oh 00:03:32.879 --> 00:03:39.519 no so these are higher capacity lower 00:03:36.799 --> 00:03:44.319 performance 4610s these are SATA 00:03:42.319 --> 00:03:48.480 it has taken all of my self-control to not open this thing up yet i actually 00:03:46.000 --> 00:03:50.959 don't even know exactly what CPU is in this freaking thing 00:03:49.840 --> 00:03:56.080 in fact okay that's interesting i didn't know 00:03:53.040 --> 00:03:59.439 that there were two cpus in this thing 00:03:56.080 --> 00:04:01.480 we requested a demo unit back in july so 00:03:59.439 --> 00:04:06.879 i'm thinking they are probably 00:04:03.200 --> 00:04:09.040 cascade lake cpus with barlow pass dimms 00:04:06.879 --> 00:04:13.280 but they could also be first gen apache pass dimms which are about 80 percent as 00:04:11.439 --> 00:04:17.759 performant to be clear they're still going to be pretty flipping high 00:04:14.480 --> 00:04:20.079 performance and i'm expecting them to be 00:04:17.759 --> 00:04:22.400 pretty high capacity let's have a look here 00:04:21.199 --> 00:04:31.440 oh oh my check this out ladies and gentlemen 00:04:26.560 --> 00:04:34.400 that right there is a 512 00:04:31.440 --> 00:04:40.000 Gigabyte dim but notice that i didn't say 512 00:04:37.600 --> 00:04:45.120 Gigabyte memory module if you look closely at all the memory 00:04:42.720 --> 00:04:50.800 that's stacked up in this thing well do the math if all of these were 512 gigs 00:04:48.560 --> 00:04:54.080 that would be 12 terabytes of memory that's more than these xeon cpus even 00:04:52.960 --> 00:05:01.040 support so if you look closely check this out 00:04:57.840 --> 00:05:04.080 half of them are traditional ddr4 memory 00:05:01.040 --> 00:05:07.759 modules so these ones right here 32 gig 00:05:04.080 --> 00:05:09.120 ecc registered dimms from micron and the 00:05:07.759 --> 00:05:18.160 other half are this this is Intel's dc pmm or data center 00:05:14.160 --> 00:05:20.479 persistent memory module and on these 00:05:18.160 --> 00:05:24.160 it is not dram there's no memory on them i mean there's 00:05:22.639 --> 00:05:29.919 memory in the sense that you can like store things on them and the system can 00:05:26.479 --> 00:05:32.240 work with that data but no dram memory 00:05:29.919 --> 00:05:37.199 so it actually uses the same optane chips that you would find in something 00:05:34.160 --> 00:05:39.199 like a high performance storage drive or 00:05:37.199 --> 00:05:46.160 one of those little obtain memory modules that Intel sells as like a nitro 00:05:42.240 --> 00:05:46.160 boost for your mechanical hard drive 00:05:46.880 --> 00:05:50.240 oh dear lord no 00:05:51.199 --> 00:05:59.680 oh my god how much does it cost wow what a good question um well i think i found 00:05:57.039 --> 00:06:04.000 a four pack of these modules for nine grand 00:06:00.960 --> 00:06:06.639 uh so we have 12 of them 00:06:04.000 --> 00:06:10.639 just under 30 dollars for the optane modules alone got probably 00:06:08.720 --> 00:06:14.639 another couple grand in regular memory let's call it 30 grand total in memory 00:06:13.039 --> 00:06:18.639 depending on what cpus these are they could be anywhere from you know five to 00:06:16.960 --> 00:06:21.919 ten grand each i think it's pretty safe to say that 00:06:20.319 --> 00:06:26.479 this whole thing is somewhere in the neighborhood of 40 to 60 000 us dollars 00:06:24.880 --> 00:06:30.160 so no Intel will not be leaving it with us but we get to play with it 00:06:28.639 --> 00:06:36.400 it's just trippy you know like it's not that often that i encounter hardware so 00:06:33.199 --> 00:06:36.400 high end that i'm just like 00:06:37.120 --> 00:06:44.560 but like look at this these are pci express 24x slots ever seen one of those 00:06:42.479 --> 00:06:49.120 unless you're in the server space stop probably not i mean they've got them 00:06:46.080 --> 00:06:52.319 just adapted to 16x slots but these 00:06:49.120 --> 00:06:54.240 expansion slots right here or this ocp 00:06:52.319 --> 00:06:59.840 mezzanine spot right here could be used for like super high speed networking um 00:06:58.400 --> 00:07:04.080 what else we got oh i answered my question from earlier it looks like 00:07:02.000 --> 00:07:07.280 these four slots are actually configured for SATA only based on the connectors 00:07:05.919 --> 00:07:10.720 that are in them but i'm 00:07:09.440 --> 00:07:14.160 not sure if yeah if you had another board or used a pci express slot it 00:07:12.479 --> 00:07:20.160 looks like the backplane does support NVMe just uh it's a universal backplane 00:07:17.440 --> 00:07:24.000 but it's not u.3 so you can't just plug in either kind of drive regardless 00:07:22.160 --> 00:07:27.759 of what it's hooked up to okay should we power it on 00:07:26.080 --> 00:07:32.800 no we shouldn't actually what we should talk about is 00:07:29.599 --> 00:07:34.319 how these memory modules are used so 00:07:32.800 --> 00:07:39.360 there's a couple of different ways that they can be configured either in app 00:07:37.120 --> 00:07:46.160 direct mode where the system actually recognizes the dim as persistent storage 00:07:42.720 --> 00:07:48.479 just like a regular SSD but connected to 00:07:46.160 --> 00:07:52.800 a high-speed memory interface directly to the CPU 00:07:49.919 --> 00:07:58.479 or they can operate in memory mode where the system recognizes them as very very 00:07:55.840 --> 00:08:03.479 high capacity memory modules and uses them in exactly the same way now as you 00:08:01.520 --> 00:08:10.080 guys can imagine intercompatibility of a memory slot 00:08:05.840 --> 00:08:11.840 between dram and storage chips is not 00:08:10.080 --> 00:08:15.919 the kind of thing that happens overnight it was actually three and a half years 00:08:13.680 --> 00:08:21.520 ago that i first attended an octane briefing at Intel's folsom campus the 00:08:18.479 --> 00:08:24.000 idea seemed pretty sound optane comes in 00:08:21.520 --> 00:08:28.560 here with lower capacities and higher cost than the nand that's traditionally 00:08:26.160 --> 00:08:33.760 found in solid state drives but then higher capacities and lower cost 00:08:31.360 --> 00:08:37.919 relative to dram which is what you would normally find on a memory module as for 00:08:36.000 --> 00:08:43.760 performance they projected latencies somewhere in between the two but closer 00:08:40.399 --> 00:08:46.399 to dram than to nand and the pricing at 00:08:43.760 --> 00:08:52.080 least has somewhat held true in the real world i found that it's a little under 00:08:48.640 --> 00:08:53.600 half the price of a memory module and 00:08:52.080 --> 00:08:59.839 definitely available at higher capacities it should be noted though that these you know retail online prices 00:08:58.000 --> 00:09:03.200 are rarely what would be paid by an actual enterprise or a data center 00:09:01.680 --> 00:09:06.080 customer oh i didn't really think of this before we fire this up i'm kind of 00:09:04.880 --> 00:09:10.160 going to need a boot drive so i'll have to run and grab an m.2 to throw in here 00:09:08.399 --> 00:09:14.480 and that's not as crazy as it sounds i mean yes i know Linus this thing is full 00:09:12.800 --> 00:09:19.200 of storage why don't you just install an os on it and off you go well 00:09:17.279 --> 00:09:23.839 that's not really how a device like this is intended to be used i know it does 00:09:21.040 --> 00:09:29.839 have terabytes of storage in both the bays at the front and the memory slots 00:09:26.720 --> 00:09:32.160 but this is more of a compute node and 00:09:29.839 --> 00:09:36.640 all these tiers of storage are meant to keep the CPU chock full of data to 00:09:34.959 --> 00:09:41.519 crunch so that it can run at peak efficiency so you've actually got five 00:09:39.279 --> 00:09:45.920 tiers of storage in here you've got the sram so that's your cache on the CPU 00:09:44.000 --> 00:09:50.080 you've got your dram which is in half of these memory slots you've got your 00:09:48.000 --> 00:09:55.440 octane memory so that's in the other half you've got your NVMe ssds over here 00:09:53.760 --> 00:10:01.120 and then finally you've got your SATA ssds over here so whatever the CPU needs 00:09:58.399 --> 00:10:06.640 the quickest access to stays closest to it and whatever is less important falls 00:10:03.680 --> 00:10:09.440 away onto these slower tiers oh wait 00:10:07.680 --> 00:10:13.519 it's not that loud because it's not actually on 00:10:11.680 --> 00:10:17.290 fans are powered up even before you turn it on 00:10:14.800 --> 00:10:22.440 here we go 00:10:29.040 --> 00:10:34.800 that's actually quieter than i expected 00:10:33.040 --> 00:10:38.399 it's pretty good oh there it goes 00:10:37.360 --> 00:10:42.000 hey it survived 00:10:40.640 --> 00:10:47.200 dropping into the BIOS we're running xeon platinum 8260ls and this poor thing 00:10:45.600 --> 00:10:51.519 has no idea what's going on with the memory here it's like oh yeah you got uh 00:10:49.600 --> 00:10:57.920 three terabytes of RAM except that if we pop in here ah yes 00:10:54.720 --> 00:11:00.480 these are the real numbers 384 gigs of 00:10:57.920 --> 00:11:06.880 dram and six terabytes of Intel's optane persistent 00:11:03.519 --> 00:11:09.360 memory modules now BIOS optimizations to 00:11:06.880 --> 00:11:13.519 make this work are important both your settings 00:11:10.560 --> 00:11:21.040 and your vendor firmware lenovo seems to recommend anywhere from a 1 to 4 to 1 to 00:11:17.279 --> 00:11:22.480 16 ratio of dram to persistent memory 00:11:21.040 --> 00:11:27.279 depending on what you're doing and as for Intel's guidance they say that 00:11:24.720 --> 00:11:32.800 applications like redis imdb run well with an eight to one config while legacy 00:11:29.680 --> 00:11:34.959 databases like microsoft sql runs ideal 00:11:32.800 --> 00:11:38.720 in like a four to one config there's also times where two to one works best 00:11:36.880 --> 00:11:43.519 if you want to minimize cache misses so that's times when the CPU is trying to 00:11:41.600 --> 00:11:47.680 find something in dram but it's already been demoted to persistent memory 00:11:46.560 --> 00:11:52.640 i mean this is mind-blowing to me like my mind 00:11:50.079 --> 00:11:58.000 was already blown way back in the athlon xp days when i found out that you could 00:11:54.800 --> 00:12:00.399 run dual channel with three sticks 00:11:58.000 --> 00:12:04.320 if you have one high capacity stick and then two half capacity sticks i was like 00:12:03.040 --> 00:12:09.440 what this another level of mind blown totally 00:12:07.440 --> 00:12:13.680 different capacities and not even the same kinds of chips on the dimms that's 00:12:12.160 --> 00:12:19.040 hilarious this thing is so not designed to boot 00:12:15.839 --> 00:12:21.839 off of a local drive my m.2 showed up as 00:12:19.040 --> 00:12:26.160 UEFI miscellaneous device in the boot options it was configured to boot from 00:12:23.600 --> 00:12:29.760 network which makes way more sense but hopefully it'll do it my poor SSD is 00:12:28.720 --> 00:12:32.639 like what is this stuff 00:12:32.800 --> 00:12:38.959 we might have to do a fresh install i've got some drivers on this thing that are 00:12:35.920 --> 00:12:41.040 not playing nicely AMD ryzen 00:12:38.959 --> 00:12:46.160 masterdriver.sis crashed 00:12:43.440 --> 00:12:51.920 it was on an AMD system before just installed chipset drivers 00:12:49.279 --> 00:12:55.440 so everything is picking up correctly now 00:12:53.120 --> 00:13:00.560 here's what i want to know though when i open up task manager 00:12:57.600 --> 00:13:00.560 what am i going to see 00:13:01.040 --> 00:13:09.279 aha okay so we got 48 CPU cores yeah that's 00:13:06.320 --> 00:13:13.760 all as expected pretty sweet and we got 00:13:10.480 --> 00:13:16.399 two terabytes apparently of memory 00:13:13.760 --> 00:13:19.680 with 4.3 terabytes hardware reserved 00:13:18.480 --> 00:13:24.160 for 6.3 terabytes how does this math work 00:13:22.480 --> 00:13:29.279 from what i can glean our persistent memory modules seem to be just operating 00:13:26.560 --> 00:13:34.000 as expanded system memory but even within that mode there are multiple 00:13:31.440 --> 00:13:38.639 modes so there's a bandwidth optimized mode and a latency optimized mode and 00:13:36.880 --> 00:13:43.200 then Intel actually came out with a balanced mode after launch that they 00:13:40.800 --> 00:13:48.800 said works pretty darn well where it uses the dram as a cache and then the 00:13:46.160 --> 00:13:53.440 optane persistent memory as like a large dumping ground giving you dram like 00:13:51.360 --> 00:13:58.480 performance depending on the workload even though optane is an order of 00:13:55.440 --> 00:14:01.040 magnitude slower in terms of latency 00:13:58.480 --> 00:14:06.160 now obviously benchmarking something like this isn't as simple as firing up 00:14:03.600 --> 00:14:10.079 cinebench and being like yeah you know 00:14:08.240 --> 00:14:15.760 it's really good it's really fast or it's not very good so guys stay tuned 00:14:13.120 --> 00:14:20.800 this is just the unboxing making sure it works oh my gosh this thing's crazy and 00:14:18.959 --> 00:14:24.240 Anthony or Jake is probably going to end up putting this thing through its paces 00:14:22.320 --> 00:14:27.920 over the next little while which raises the question what kind of benchmarks 00:14:26.160 --> 00:14:33.600 would they even run who's the audience for this well if you had a very large database 00:14:31.440 --> 00:14:37.680 that you wanted to run in memory for extreme performance you could run it in 00:14:35.519 --> 00:14:43.519 memory mode if for whatever reason you needed extremely fast storage like a 00:14:41.440 --> 00:14:47.279 really fast storage device you could run it in storage mode or block mode 00:14:46.399 --> 00:14:52.160 i mean yeah you could also just use optane in 00:14:50.160 --> 00:14:56.079 an NVMe device like what we've actually got installed on the front here but the 00:14:54.320 --> 00:15:00.320 advantage in this case is that instead of contending with pci express 00:14:58.399 --> 00:15:05.040 which is going to be a bottleneck depending what you're doing and an NVMe 00:15:02.800 --> 00:15:10.240 protocol that was designed first and foremost for nand you're communicating 00:15:07.600 --> 00:15:15.199 with your storage over the much faster memory interface that's built right into 00:15:12.160 --> 00:15:18.160 the CPU but get this it's not all boring 00:15:15.199 --> 00:15:22.720 stuff like that in 2019 you can see we're just running Windows 10 here guys 00:15:20.639 --> 00:15:26.399 microsoft rolled support for this product into Windows 10 allowing it to 00:15:25.279 --> 00:15:32.240 be used for rendering simulation and scientific 00:15:29.199 --> 00:15:35.120 tasks that are certainly heavy but not 00:15:32.240 --> 00:15:39.680 necessarily in the data center so workstations with multiple terabytes of 00:15:38.240 --> 00:15:43.040 RAM that could be very interesting for a lot 00:15:41.760 --> 00:15:50.079 of people now dims with persistent storage already 00:15:47.360 --> 00:15:54.800 exist they're called envy dim but the difference is that instead of having 00:15:52.160 --> 00:15:57.519 high speed dram and then slower nand that it can flush to when it's powered 00:15:56.720 --> 00:16:03.600 off this is just all optane all the time thanks to its much higher 00:16:02.079 --> 00:16:09.279 rate endurance so that's it for today that's the 00:16:06.399 --> 00:16:13.199 introduction to this tech holy is it ever cool and we're gonna have a follow 00:16:11.199 --> 00:16:17.440 up for you guys where we really put it through its paces and this video is 00:16:15.680 --> 00:16:23.680 brought to you of course by the real-time remote monitoring and management software that we use for our 00:16:20.720 --> 00:16:27.120 servers pulseway it works for not just servers you can deploy it on 00:16:25.040 --> 00:16:31.120 workstations laptops anything it helps you fix problems on the go by sending 00:16:29.199 --> 00:16:35.279 commands from any mobile device it's compatible with Windows mac and Linux 00:16:33.680 --> 00:16:39.440 and their single app gives you remote desktop functionality you can get 00:16:37.199 --> 00:16:43.120 real-time status monitor system resources check logged in users and 00:16:41.360 --> 00:16:46.320 network performance you can manage Windows updates their endpoint 00:16:44.959 --> 00:16:49.680 protection function allows you to install pulseway antivirus across 00:16:48.399 --> 00:16:54.000 systems and ensure they're fully protected at all times and you can 00:16:51.839 --> 00:16:57.680 create deploy and automate custom scripts to automate your it tasks like 00:16:56.320 --> 00:17:04.160 deployments patching security backups reports and 00:17:00.639 --> 00:17:05.520 more so try it for free at pulseway.com 00:17:04.160 --> 00:17:09.520 or through our link in the video description if you guys enjoyed this 00:17:07.439 --> 00:17:14.000 video maybe check out our last big server upgrade series petabyte project 00:17:12.079 --> 00:17:18.720 who where we rolled out a petabyte of storage in a single 4u enclosure that's 00:17:17.120 --> 00:17:22.559 just four times the thickness of this one and we did it twice