WEBVTT - TechStuff's Two Bits on 32-bit and 64-bit Systems 0:00:00.280 --> 0:00:02.960 Brought to you by the reinvented two thousand twelve Camray. 0:00:03.160 --> 0:00:08.920 It's ready. Are you get in touch with technology? With 0:00:09.000 --> 0:00:17.880 tech Stuff from how stuff dot com. Hello, everyone, Welcome 0:00:17.920 --> 0:00:20.200 to tech Stuff. My name is Chris Pollette, and I'm 0:00:20.239 --> 0:00:24.360 an editor at how stuff works dot com. And sitting 0:00:24.520 --> 0:00:28.800 just a bit across from me is senior writer Jonathan Strickland. Midnight, 0:00:29.240 --> 0:00:31.920 not a sound on the pavement. Has the moon lost 0:00:31.920 --> 0:00:37.360 her memory? She's smiling alone. This podcast will be much 0:00:37.400 --> 0:00:40.760 better than KATS Yes, I should hope, So I'm going 0:00:40.800 --> 0:00:45.080 to listen to it again and again. Anyway, So, yeah, 0:00:45.120 --> 0:00:47.639 today we're gonna talk. We had actually some requests come 0:00:47.680 --> 0:00:52.480 in about explaining thirty two bit versus sixty four bit 0:00:52.720 --> 0:00:56.040 in the terms of computers. What does that mean? What 0:00:56.360 --> 0:01:00.480 is sixty bit automatically better than thirty two bit? What's 0:01:00.520 --> 0:01:02.960 the deal behind this? Because we've seen some operating systems 0:01:03.000 --> 0:01:05.880 come out over the last several years, especially since like 0:01:05.920 --> 0:01:10.160 Windows Vista that had sixty four bit versions and thirty 0:01:10.160 --> 0:01:12.960 two bit versions and not all would work on every computer. 0:01:13.200 --> 0:01:16.200 What's up with that? Anyway? Well, the answers to those 0:01:16.280 --> 0:01:22.600 questions is basically yes, no, maybe it's a computer architecture question. 0:01:22.680 --> 0:01:26.000 As it turns out, so and and the answer is 0:01:26.600 --> 0:01:29.520 is not definitive. I mean it's sort of well anyway, 0:01:29.600 --> 0:01:31.800 let's talk about it. Okay, yeah, so let's talk about 0:01:31.800 --> 0:01:34.000 what it all means to be thirty two bit versus 0:01:34.040 --> 0:01:36.640 sixty four bit in the first place. So, well, that 0:01:36.680 --> 0:01:42.120 part's easy. We're talking about computer architecture here. Now, just 0:01:42.240 --> 0:01:44.320 on a high level, this is going to be very 0:01:44.360 --> 0:01:46.760 general for all of you. So all of you computer 0:01:46.800 --> 0:01:49.440 scientists out there, Uh, you might want to fast forward 0:01:49.440 --> 0:01:52.640 a little bit because your your eyes may start bulging 0:01:52.680 --> 0:01:56.160 if you hear me describe computers in these simplistic terms. 0:01:56.400 --> 0:01:59.600 Make yourself a sandwich. But in general, you have this 0:01:59.800 --> 0:02:03.720 thing in your computer, the central processing unit, all right, 0:02:04.040 --> 0:02:09.120 And they're basically two ways to try and make a CPU, 0:02:09.560 --> 0:02:14.080 uh do more work or or be more efficient. Um, 0:02:14.120 --> 0:02:17.120 and I'm saying basically two ways are actually more than that, 0:02:17.240 --> 0:02:20.440 especially if you go into multi core processing. But if 0:02:20.440 --> 0:02:23.680 you're talking about single core processor, you can either make 0:02:23.760 --> 0:02:27.760 the processor work faster, which means that it can operate. 0:02:27.760 --> 0:02:30.840 It could complete more operations in the same amount of 0:02:30.840 --> 0:02:35.960 time as a slower CPU. Right, So operations are done 0:02:36.040 --> 0:02:39.919 in uh in in uh cycles for a second. So 0:02:39.960 --> 0:02:42.400 how many times the clock cycles per second with that 0:02:42.480 --> 0:02:46.200 particular processor essentially means how many operations that can do, 0:02:46.320 --> 0:02:50.560 although some operations require multiple cycles. Okay, so you can 0:02:50.600 --> 0:02:53.600 make your computer go faster by putting in a faster processor. 0:02:53.919 --> 0:02:56.680 But another way computers can go faster is if they 0:02:56.720 --> 0:03:02.359 can process more information at one time than a slower 0:03:02.480 --> 0:03:05.280 process or a processor that runs at the same speed 0:03:05.320 --> 0:03:09.240 but does less information at the time. Because for a 0:03:09.320 --> 0:03:15.200 processor to to actually execute commands and to crunch numbers 0:03:15.880 --> 0:03:19.200 essentially is what a secret is doing. It's computing. Yeah, 0:03:19.320 --> 0:03:23.720 it's pulling information from the computer's memory and then executing 0:03:23.840 --> 0:03:27.200 a series of commands that are dictated by whatever the 0:03:27.240 --> 0:03:30.640 application that's running says it has to do, and then 0:03:30.680 --> 0:03:34.400 you get the output. All right, So, if you have 0:03:34.960 --> 0:03:38.520 a narrow pathway, then only so much information can come 0:03:38.560 --> 0:03:40.960 through at a time. If you make that pathway wider, 0:03:41.040 --> 0:03:43.800 more information can come in and that same amount of time, 0:03:43.840 --> 0:03:47.040 the information is not necessarily traveling faster, is just more 0:03:47.040 --> 0:03:49.240 of they can go through. So if we use the 0:03:49.480 --> 0:03:54.520 handy dandy, let's talk about a building metaphor that I 0:03:54.520 --> 0:03:56.640 always like to go with. Let's say you've got a building, 0:03:57.040 --> 0:04:00.160 it's got a doorway that's one person wide, and got 0:04:00.200 --> 0:04:01.720 a whole bunch of people who want to go in, 0:04:02.360 --> 0:04:04.480 uh to that building, but they all have to move 0:04:04.680 --> 0:04:09.040 at a specific rate. They cannot run the been the 0:04:09.080 --> 0:04:11.760 hall monitors are there and they're telling everyone no running. 0:04:12.760 --> 0:04:14.760 Then it's gonna take a certain amount of time for 0:04:14.800 --> 0:04:17.320 all those people to get into the building filing in 0:04:17.600 --> 0:04:22.279 single file through that one person wide opening. Now let's 0:04:22.320 --> 0:04:25.120 take that same building, but we've done some reconstruction on it. 0:04:25.200 --> 0:04:28.200 We've made that building so that there are three people 0:04:28.440 --> 0:04:32.440 can walk side by side into that and you still 0:04:32.480 --> 0:04:35.160 tell everyone no running, so they're moving at the same speed, 0:04:35.200 --> 0:04:37.760 but now more people can go into the building in 0:04:37.800 --> 0:04:40.560 the same amount of time as it took. You know, 0:04:40.600 --> 0:04:42.560 you're you're gonna take less time to get everybody in 0:04:42.600 --> 0:04:46.280 than it took for the single person version of that building. 0:04:47.000 --> 0:04:50.440 So that's kind of the idea behind this computer architecture 0:04:50.440 --> 0:04:52.960 with thirty two bit versus sixty four bit at a 0:04:53.120 --> 0:04:56.920 very high level. Yeah, and the thing is, it's, uh, 0:04:56.960 --> 0:05:00.760 there are a number of things that affect U in 0:05:00.800 --> 0:05:03.719 your overall computer architecture. There are a number of things 0:05:03.720 --> 0:05:08.159 that affect how much information can be handled by the 0:05:08.200 --> 0:05:11.240 CPU at a time. For example, you know all the 0:05:11.279 --> 0:05:15.200 different cabling and everything else that's in there. I mean, 0:05:15.400 --> 0:05:18.320 you're if you have a better graphics, faster graphics processor, 0:05:18.400 --> 0:05:21.760 your graphics processor will handle more graphics. But we're speaking 0:05:21.800 --> 0:05:26.039 specifically of the CPU and not of the cables that 0:05:26.160 --> 0:05:28.400 run that information to the different parts of the computer 0:05:28.440 --> 0:05:31.800 and those things. We're talking about the actual processor itself. 0:05:32.360 --> 0:05:36.560 And there is one other thing, however, that uh, that 0:05:36.680 --> 0:05:42.000 it needs to handle this and and that is forgotten 0:05:42.040 --> 0:05:49.120 what it was? What is it? Data bus? Memory? I remember? Now? Well, 0:05:49.160 --> 0:05:52.520 the data bus is the the the pathway between memory 0:05:52.680 --> 0:05:56.000 and the CPU. Well, yeah, that's the thing. See that 0:05:56.000 --> 0:05:59.719 that pathway has to be ample enough to to carry 0:06:00.520 --> 0:06:05.120 uh information. But the memory, the amount of memory you have, 0:06:05.800 --> 0:06:10.560 and how your CPU handles memory is pivotal to how 0:06:10.640 --> 0:06:15.240 well your computer can handle instruction. Yeah. So that's when 0:06:15.240 --> 0:06:18.119 we talk about computer architecture. You're not just talking about 0:06:18.160 --> 0:06:21.919 one component in the computer. If you put a sixty 0:06:21.960 --> 0:06:25.440 four bit processor in a computer and you didn't change 0:06:25.480 --> 0:06:29.279 anything else, it wouldn't matter. It wouldn't matter, Yeah, because 0:06:29.279 --> 0:06:31.240 it because even though you've got a sixty four bit 0:06:31.279 --> 0:06:33.400 processor and there the rest of the computer is not 0:06:33.640 --> 0:06:37.080 designed with the architecture that's necessary to take advantage of that. 0:06:37.560 --> 0:06:40.880 So with the memory, you you know, sixty four bit 0:06:40.920 --> 0:06:44.640 processor would be able to access more memory because the 0:06:44.680 --> 0:06:47.200 sixty four bit that talks about how much information can 0:06:47.440 --> 0:06:50.960 come through, right, and so it's effectively twice as much 0:06:50.960 --> 0:06:56.240 as the thirty two bit. Right, so you've got what 0:06:56.600 --> 0:07:00.479 go ahead, I heard the inhale of stopping anyway. The so, 0:07:00.480 --> 0:07:02.920 so the data bus is it's not a bus like 0:07:03.040 --> 0:07:06.680 get on the bus, you know, or deserts or desert bus. 0:07:07.600 --> 0:07:10.200 It will drive for eight hours and get one point. Yeah, yeah, 0:07:10.360 --> 0:07:14.400 well who Tucson. So yeah, the data bus is essentially 0:07:14.400 --> 0:07:16.760 the pathway from the memory to the CPU. So you 0:07:17.400 --> 0:07:20.840 with a sixty four bit system, you're gonna have more memory, 0:07:20.880 --> 0:07:23.800 more random access memory, more RAM You're going to have 0:07:24.200 --> 0:07:27.360 a larger data bus. The data bus that's the sixty 0:07:27.360 --> 0:07:29.480 four bit data bus that is going to allow sixty 0:07:29.520 --> 0:07:33.440 four bit information to pass through as opposed to thirty 0:07:33.480 --> 0:07:36.040 two bit, and then the sixty four bit processor that 0:07:36.080 --> 0:07:39.760 can process information. This does not work well for every 0:07:39.840 --> 0:07:43.280 kind of computer problem. There are certain kinds of computer 0:07:43.320 --> 0:07:47.480 problems that just don't need that. It's not that, you know, 0:07:47.560 --> 0:07:50.880 it's not that it's harmful, it just isn't beneficial. So 0:07:50.960 --> 0:07:53.120 in other words, let's say that we go back to 0:07:53.160 --> 0:07:56.480 that building example. All right, and let's say that you 0:07:56.560 --> 0:07:58.840 only have one person who has to get in the building. Well, 0:07:58.880 --> 0:08:01.640 it doesn't matter how why the doorway is. If there's 0:08:01.680 --> 0:08:04.080 no obstruction, then that person is going to get in 0:08:04.160 --> 0:08:06.560 the building at the same speed. Whether the doorways one 0:08:06.560 --> 0:08:09.920 person wide or three people wide. Well, same sort of thing. 0:08:09.960 --> 0:08:15.600 If you have a computer application that doesn't require massive uh, 0:08:16.480 --> 0:08:19.200 it doesn't require the CPU to constantly be pulling information 0:08:19.240 --> 0:08:23.280 from memory, then it's not gonna see a big benefit 0:08:23.440 --> 0:08:25.880 to switching from thirty two bit system to a sixty 0:08:25.880 --> 0:08:28.960 four bit system. Oh and I forgot another piece. We 0:08:28.960 --> 0:08:31.880 were talking about computer architecture. With all the physical hardware, 0:08:32.120 --> 0:08:34.640 you also have to have an operating system that can 0:08:34.679 --> 0:08:39.360 take advantage of the sixty four bit architecture. So if 0:08:39.400 --> 0:08:41.400 you have a sixty four bit system, you would need 0:08:41.440 --> 0:08:43.400 to get an operating system that's also a sixty four 0:08:43.400 --> 0:08:46.120 bit operating system if you wanted to run at that 0:08:46.240 --> 0:08:49.600 full speed. Most sixty four bit systems are capable at 0:08:49.679 --> 0:08:54.839 running thirty two bit UH software UM usually through either 0:08:55.559 --> 0:08:57.440 UH there's like a there might be a thirty two 0:08:57.440 --> 0:09:00.839 bit core that's incorporated in the TOM itself, or it 0:09:00.920 --> 0:09:03.960 might be that there's an emulator running. But usually a 0:09:04.000 --> 0:09:06.360 sixty four bit system is capable of running thirty two 0:09:06.400 --> 0:09:10.160 bits software. If it weren't, then you would rapidly discover 0:09:10.280 --> 0:09:14.080 that most software would be unusable because not not everyone 0:09:14.120 --> 0:09:16.880 has upgraded up to sixty four bit yet. Before you 0:09:16.920 --> 0:09:18.719 send us a list of all the software that you've 0:09:18.760 --> 0:09:20.720 tried on your sixty four bit system that doesn't work, 0:09:20.760 --> 0:09:23.600 remember your mileage may vary. Some restrictions apply. It also 0:09:23.640 --> 0:09:26.920 depends heavily upon the actual operating system and how it 0:09:27.000 --> 0:09:29.480 was providing that support. Because again, if you're talking about 0:09:29.520 --> 0:09:33.000 emulators that does that's not a one size fits all approach, 0:09:33.360 --> 0:09:36.600 you know, So go ahead. I was gonna say, here's 0:09:36.600 --> 0:09:40.160 the interesting part about the thirty two bit versus sixty 0:09:40.160 --> 0:09:45.040 four bit systems. Thirty two bit systems can only address 0:09:45.559 --> 0:09:47.840 a certain amount well, all of them can address a 0:09:47.840 --> 0:09:53.480 certain amount of computer memory of RAM, And with thirty 0:09:53.520 --> 0:09:58.640 two bit systems, you can only address for gigabytes of RAM, 0:09:58.679 --> 0:10:03.840 and back in the day, everyone thought four gigabytes a RAM, Wow, 0:10:04.160 --> 0:10:08.040 we'll never need that much. That that famous quote attributed 0:10:08.080 --> 0:10:12.199 to Bill Gates, which apparently he never said about how much. 0:10:12.440 --> 0:10:15.760 I forgotten how much it was, like megabytes or something 0:10:15.760 --> 0:10:20.000 like that. But um, but yeah, people said, well, that's 0:10:20.040 --> 0:10:22.400 that's plenty for what we do. But the thing about 0:10:22.440 --> 0:10:25.520 it is, now we're using computers to do high end 0:10:25.559 --> 0:10:30.800 graphics work and high end soundwork. Um, scientific calculations, scientific calculations. 0:10:30.800 --> 0:10:36.280 We expect our game machines to render beautiful three D 0:10:36.520 --> 0:10:39.840 graphics where where the hair on people's heads moves with 0:10:39.880 --> 0:10:43.079 the breeze and the leaves, there's no clipping or effect. 0:10:43.120 --> 0:10:46.040 It doesn't affect the physics engine at all. Yeah. Yeah, 0:10:46.080 --> 0:10:49.959 And the thing is, at a certain point, uh, you're 0:10:50.000 --> 0:10:52.439 you're kind of looking for more from the system because 0:10:53.080 --> 0:10:57.760 we're able to do these things now. So they've enabled processors, 0:10:57.800 --> 0:11:01.040 and these sixty four bit processors are not brand new. 0:11:01.120 --> 0:11:03.840 They didn't come out in These have been on the 0:11:03.880 --> 0:11:07.360 market for for several years and in fact, the earliest 0:11:07.360 --> 0:11:11.359 ones date from the seventies. Yeah. Yeah, the Kraze supercomputer, 0:11:11.400 --> 0:11:15.839 the original kraz one supercomputer had a sixty four bit architecture. Yes, so, 0:11:15.920 --> 0:11:19.679 while um so, while thirty two bit machines can address 0:11:20.760 --> 0:11:24.240 for gigabytes of RAM, a sixty four bit machine and 0:11:24.280 --> 0:11:26.880 this sort of sounds like our I p v six 0:11:27.040 --> 0:11:33.439 thing can address seventeen point two billion gigabytes of RAM, 0:11:33.600 --> 0:11:36.800 which is far more than any of our machines will 0:11:36.840 --> 0:11:39.360 hold at this point. Now, I've seen machines that will 0:11:39.400 --> 0:11:43.200 hold sixty four gigabytes of RAM. They're probably some really 0:11:43.240 --> 0:11:45.440 high end machines that will hold even more than that, 0:11:45.800 --> 0:11:49.800 but it's still far more than the operating system and 0:11:50.480 --> 0:11:55.000 computer hardware can access right now. So basically, this is 0:11:55.040 --> 0:11:58.640 a build for the future, the immediate foreseeable future, and 0:11:58.640 --> 0:12:01.880 the more. Um. If you've ever heard somebody say, hey, 0:12:01.920 --> 0:12:03.760 I know, if you really want to speed up your computer, 0:12:04.240 --> 0:12:06.400 a cheap way to do that is to add more RAM. Well, 0:12:06.440 --> 0:12:09.319 in general that's true. If you have more memory space, 0:12:09.360 --> 0:12:13.480 that gives your computer a lot more room to handle uh, 0:12:13.800 --> 0:12:17.440 regular calculations, because keep in mind that your operating system 0:12:17.520 --> 0:12:19.640 is taking up a certain amount of RAM and all 0:12:19.679 --> 0:12:23.720 the other operating stuff under the UM that that's hanging 0:12:23.760 --> 0:12:27.640 out with it, like say um virus protection software and 0:12:27.679 --> 0:12:29.320 other things that you use on a daily basis, and 0:12:29.320 --> 0:12:33.000 then you open up Photoshop to work on on stuff 0:12:33.000 --> 0:12:36.480 and it runs incredibly slow. And why, oh man, why 0:12:36.480 --> 0:12:39.079 does this run so slow? Well, if it had more memory, 0:12:39.440 --> 0:12:41.920 it would be far easier for the computer to allocate 0:12:42.000 --> 0:12:46.320 and resources to Photoshop because it's already got a bunch 0:12:46.320 --> 0:12:48.560 of stuff in memory. So yeah, it's it's it's both 0:12:48.600 --> 0:12:52.080 the processor speed itself and the speed at which it 0:12:52.080 --> 0:12:54.240 can or the amount of memory it can access a 0:12:54.280 --> 0:12:56.440 think of a huge difference. Yeah, think of it this way, 0:12:56.520 --> 0:13:01.719 like your your computer. If if you're processor had to 0:13:02.760 --> 0:13:05.480 access your hard drive every time you need to pull 0:13:05.559 --> 0:13:09.240 up information, it would slow everything down, right, Like if 0:13:09.280 --> 0:13:11.640 it had to go into your hard drive in order 0:13:11.640 --> 0:13:14.960 to pull whatever the information is in order to execute 0:13:15.000 --> 0:13:17.120 the file you just said, or the execute the command 0:13:17.160 --> 0:13:20.719 you just made, then it would slow things down to 0:13:20.840 --> 0:13:24.079 a crawl. So if you were playing a game, for example, 0:13:24.160 --> 0:13:28.040 and you press the jump button and the and so 0:13:28.120 --> 0:13:31.040 you've you've executed the command. You've pressed the button that's 0:13:31.080 --> 0:13:34.040 going to cause your character to jump. Apparently that character 0:13:34.080 --> 0:13:39.600 is Mario, then the jump man. The computer will then 0:13:39.640 --> 0:13:41.800 take that command, it would have to search your hard 0:13:41.880 --> 0:13:45.280 drive to find out all right, I've been given this command, 0:13:45.320 --> 0:13:48.000 here's the sub parameters that the game is in right now. 0:13:48.360 --> 0:13:51.880 What happens next? It would get that information, process it, 0:13:51.920 --> 0:13:53.640 and then send it back to you, and this would 0:13:53.679 --> 0:13:56.280 take a long time. RAM what it does is it 0:13:56.320 --> 0:13:59.520 allows you allows the computer to pull the essentially the 0:13:59.520 --> 0:14:02.040 most pertinent information to whatever is going on right then 0:14:02.080 --> 0:14:05.679 and there to be in a temporary storage space so 0:14:05.720 --> 0:14:09.040 that the processor doesn't have to access the hard drive 0:14:09.320 --> 0:14:12.240 in order to load stuff. It just accesses RAM. And 0:14:12.280 --> 0:14:15.160 that's much faster because you know the RAM is just 0:14:15.200 --> 0:14:17.760 going to be there for the duration of the instance 0:14:17.800 --> 0:14:21.720 that you're on, like until you shut your computer down. UM. 0:14:21.880 --> 0:14:24.480 This is also why if you're playing a game on 0:14:24.520 --> 0:14:27.000 a console and you get to a new level and 0:14:27.080 --> 0:14:30.240 you get that loading screen, well, essentially it's loading that 0:14:30.520 --> 0:14:34.560 information into the consoles RAMS so that when you're playing 0:14:34.800 --> 0:14:37.280 it doesn't have to refer back to the hard drive 0:14:37.400 --> 0:14:40.880 and and that would impact your experience. So that's the 0:14:40.880 --> 0:14:42.960 same sort of idea. And now with the sixty four 0:14:43.000 --> 0:14:46.200 bit system, what you've done is dramatically increase the amount 0:14:46.200 --> 0:14:50.600 of RAM your system can potentially have, which means the 0:14:50.720 --> 0:14:53.160 CPU will not have to go back to the hard 0:14:53.240 --> 0:14:56.120 drive as frequently. Yeah, and the thing is, I mean 0:14:56.360 --> 0:14:58.640 load more information all at one time. Sorry, no, no, 0:14:58.720 --> 0:15:02.400 I'm sorry. I didn't realize, but my brain clicked. I 0:15:02.440 --> 0:15:04.680 had to go back to hard drive space. I see, 0:15:04.760 --> 0:15:08.400 I see where we should increase your RAM. So, um, 0:15:08.440 --> 0:15:13.480 I've been trying well, um, and and this is great. 0:15:13.560 --> 0:15:15.680 You know. Of course, you can always speed stuff up 0:15:15.680 --> 0:15:20.600 by closing things that you're not using, you know, but uh, this, 0:15:20.680 --> 0:15:24.080 this presents a real advantage for people who are are 0:15:24.280 --> 0:15:26.680 doing things that are memory heavy, or people who need 0:15:26.720 --> 0:15:29.200 to keep multiple programs open. Say you're editing an article 0:15:29.240 --> 0:15:32.440 and you have your word processor and your graphics programs. 0:15:32.440 --> 0:15:34.520 You can do the photos that go along with the article, 0:15:34.560 --> 0:15:36.960 and you have your email open. I've got it to 0:15:37.040 --> 0:15:39.960 do list already. You don't have to drive at home 0:15:40.120 --> 0:15:41.880 like that. But yeah, I mean you're working on all 0:15:41.880 --> 0:15:45.280 those things simultaneously. If you have enough RAM, you should 0:15:45.280 --> 0:15:47.040 be able to work fairly quickly as you as you 0:15:47.080 --> 0:15:49.760 go from one back and forth, you know, to the other. 0:15:50.040 --> 0:15:53.360 Because it's already loaded into RAM, the computer doesn't have 0:15:53.400 --> 0:15:56.520 to go and search for stuff. So let's use Let's 0:15:56.600 --> 0:15:59.120 use my home computer as an example. UM. It's about 0:15:59.120 --> 0:16:01.720 three years old at the time we're recording this UM, 0:16:01.760 --> 0:16:05.760 and it has a physical memory capacity of four gigabytes 0:16:05.760 --> 0:16:08.120 of RAM. Now I have an operating system that will 0:16:08.200 --> 0:16:11.200 run in either thirty two bit or sixty four bit mode. 0:16:11.840 --> 0:16:14.760 The question is should I boot into sixty four bit 0:16:14.800 --> 0:16:16.720 mode or should I just default to thirty two bit 0:16:18.400 --> 0:16:20.640 depending on what you're using. Actually, i'd say just default 0:16:20.680 --> 0:16:24.200 the thirty two bit because it won't even I can't 0:16:24.240 --> 0:16:27.520 even take advantage of the sixty four bit advantage of 0:16:27.760 --> 0:16:30.600 being able to address more RAM because I don't even 0:16:30.600 --> 0:16:33.240 have the capacity for more than four gigabytes and RAM. 0:16:33.560 --> 0:16:36.120 It doesn't make any sense to do that. But UM, 0:16:36.160 --> 0:16:39.200 and you can have a top ended machine, but if 0:16:39.200 --> 0:16:42.360 you're running an older operating system on it that won't 0:16:42.640 --> 0:16:45.560 run in sixty four bit mode, you're not able to 0:16:45.560 --> 0:16:48.040 take advantage of it. So, as Jonathan pointed out earlier, 0:16:48.080 --> 0:16:50.520 you have to have the machine, you have to have 0:16:50.800 --> 0:16:53.600 more memory than for gigabytes, and you have to have 0:16:53.680 --> 0:16:58.440 the operating system basically to take advantage of these benefits. 0:16:58.440 --> 0:17:01.280 But if you do that will really help you out. Yeah, Like, 0:17:01.360 --> 0:17:03.920 let's say that you want to do some heavy duty 0:17:04.040 --> 0:17:06.760 video editing and and let's see you're working on a 0:17:06.760 --> 0:17:10.880 feature link film. Well, the benefit to a sixty four 0:17:10.880 --> 0:17:12.720 bit system is that you would be able to to 0:17:13.080 --> 0:17:17.360 load a lot more footage in a single go than 0:17:17.400 --> 0:17:19.320 you would if you had a thirty two bit system. 0:17:19.359 --> 0:17:22.119 It would just be much faster, much more efficient. And 0:17:22.119 --> 0:17:26.359 it's not again necessarily because the processor is faster. Now, grant, 0:17:26.400 --> 0:17:28.879 a faster processor also helps things a lot. And then 0:17:28.920 --> 0:17:32.160 we've talked in the past a bit about multi core processors, 0:17:32.240 --> 0:17:36.960 which uh seem to give seem to be faster, even 0:17:36.960 --> 0:17:39.400 though if you look at the processor speeds, they may 0:17:39.400 --> 0:17:42.159 not be that much faster than a single core processor. 0:17:42.200 --> 0:17:46.639 In that case, the reason why it's it's uh working 0:17:46.680 --> 0:17:50.200 a more efficiently is because it's dividing up computer problems 0:17:50.200 --> 0:17:53.040 into segments, and each core works on a segment of 0:17:53.080 --> 0:17:56.160 the problem and then it ends up being put together 0:17:56.240 --> 0:17:58.640 kind of like a puzzle in the end. And that's 0:17:58.680 --> 0:18:01.400 what the you know, that's why a multi core will 0:18:01.440 --> 0:18:04.480 work best for certain kinds of problems. Again, just like 0:18:04.800 --> 0:18:06.720 we were talking about with the sixty four bit versus 0:18:06.720 --> 0:18:10.480 thirty two bit, a multi core processor isn't necessarily going 0:18:10.520 --> 0:18:14.960 to execute every single application at a faster speed than 0:18:15.640 --> 0:18:19.480 a comparable single core processor because some just don't. Some 0:18:19.520 --> 0:18:23.440 problems just don't break down into components. Uh. The ones 0:18:23.480 --> 0:18:26.960 that do we call parallel problems. And uh, in in 0:18:27.160 --> 0:18:30.199 case of grid computing, when you're talking about things like 0:18:30.800 --> 0:18:36.640 folding proteins, you call them embarrassingly parallel problems. I'm sorry, 0:18:36.720 --> 0:18:39.720 didn't mean to bring up the subject. But anyway, Uh, 0:18:39.920 --> 0:18:46.959 that's that's a that's another key element to computer speeds. So, yeah, 0:18:47.200 --> 0:18:50.720 sixty four bit operating systems. When when Windows came out 0:18:50.760 --> 0:18:53.520 with Windows Vista for six or four bit Windows Vista, 0:18:54.000 --> 0:18:56.280 there were some problems. Okay, first of all, there were 0:18:56.280 --> 0:19:01.760 problems with within Windows Vista, right, that operating system got 0:19:01.800 --> 0:19:04.680 a really bad name pretty quickly because there were a 0:19:04.760 --> 0:19:09.520 lot of name Oh I'm sorry, I'm just saying that 0:19:09.560 --> 0:19:14.200 they had a reputation for being not the best operating system. 0:19:14.240 --> 0:19:17.199 There were a lot of features that people didn't care for, 0:19:17.359 --> 0:19:19.520 and there were a lot of problems with its supporting 0:19:19.560 --> 0:19:22.560 certain kinds of software versus not supporting other kinds. And 0:19:22.600 --> 0:19:27.040 it's not yeah, right, so but the sixty four bit 0:19:27.080 --> 0:19:29.520 system when it came out, there were even more problems, 0:19:29.560 --> 0:19:31.040 and part of it was because it was, you know, 0:19:31.080 --> 0:19:35.600 fairly young for the personal computing era. Against sixty four 0:19:35.640 --> 0:19:38.360 bit architecture had been around for for more than a decade, 0:19:38.920 --> 0:19:42.040 but but the actual use of it in personal computers 0:19:42.080 --> 0:19:45.560 was pretty much brand new when the sixty four bit 0:19:45.560 --> 0:19:50.360 Windows Vista version came out. Since then, we've seen computer 0:19:50.440 --> 0:19:55.080 engineers really kind of optimized operating systems for sixty four bit, 0:19:55.600 --> 0:19:59.320 so it's not as big a problem now. Unix had 0:19:59.320 --> 0:20:01.679 a leg up a are pretty much everybody else on 0:20:01.720 --> 0:20:05.200 that one. But now we're seeing it with other systems, 0:20:05.240 --> 0:20:10.919 not just not just Unix or or its variants. So 0:20:12.119 --> 0:20:15.199 should you go out and buy a sixty four bit system, 0:20:15.400 --> 0:20:20.640 My suggestion would be unless your depends. Yeah, unless you're 0:20:20.680 --> 0:20:24.680 really working with some heavy duty videos software, you're doing 0:20:24.680 --> 0:20:28.080 scientific calculations, or you just want the most screaming video 0:20:28.160 --> 0:20:31.640 games ever made, you probably don't need to worry about 0:20:31.680 --> 0:20:33.560 it too much. Because the thing about video game machines 0:20:33.640 --> 0:20:36.720 is often you do have a dedicated graphics processor, which 0:20:36.720 --> 0:20:38.720 takes a lot of the helps. Yeah, it takes a 0:20:38.720 --> 0:20:42.040 lot of the weight off of your CPU, although you 0:20:42.280 --> 0:20:46.680 then have to add weight with a cooling system. Um. 0:20:46.720 --> 0:20:48.400 But yeah, I would say that a sixty four bit 0:20:48.440 --> 0:20:52.920 system probably is not necessary for most people right now. Now, 0:20:53.040 --> 0:20:57.560 over time, as the the whole all the parts get 0:20:57.640 --> 0:21:01.480 cheaper than the operating systems will become or standardized. We'll 0:21:01.480 --> 0:21:04.280 probably see sixty four bit become the news standard. And 0:21:04.320 --> 0:21:06.560 in that case it won't be a question of sixty 0:21:06.560 --> 0:21:09.000 four versus thirty two. It will be sixty four bit 0:21:09.080 --> 0:21:10.680 is what's in the store, so that's what you get. 0:21:11.280 --> 0:21:14.640 But right now, if you're shopping around, uh, just keep 0:21:14.640 --> 0:21:18.000 in mind that even though the number is bigger, it 0:21:18.040 --> 0:21:22.520 doesn't necessarily mean you're going to experience. Uh, it doesn't 0:21:22.520 --> 0:21:25.040 mean your computing computing experience is immediately going to be 0:21:25.080 --> 0:21:26.600 twice as fast as what it used to be on 0:21:26.640 --> 0:21:30.040 your old thirty two bit system. Yeah. Yeah, And um, 0:21:30.080 --> 0:21:34.480 as far as one systems go, I mean, the thing 0:21:34.600 --> 0:21:37.840 is for for home computing. Really, I don't think the 0:21:37.920 --> 0:21:40.880 average person needs anything like that, or or will need 0:21:40.920 --> 0:21:43.240 anything like that for quite some time. If you're trying 0:21:43.240 --> 0:21:46.119 to give sentience to your refrigerator, you may need a 0:21:46.200 --> 0:21:49.199 hundred and twenty eight system for something like you know, 0:21:49.280 --> 0:21:52.640 high end scientific computing. Well, sure, you know, super computer 0:21:52.720 --> 0:21:56.639 type stuff. If you're searching for intelligent life, possibly in 0:21:56.680 --> 0:22:02.920 this office, that joke is coming. Uh no, but yeah, 0:22:02.960 --> 0:22:05.080 I mean when you when you're already able to address 0:22:05.680 --> 0:22:10.000 seventeen exabytes of memory and you can't even fit that 0:22:10.080 --> 0:22:14.280 inside the box. Yeah, there's no way to the memory 0:22:14.320 --> 0:22:17.400 because the Yeah, you would have to have a computer 0:22:17.560 --> 0:22:21.160 the size of well, the old ones because and I'm 0:22:21.160 --> 0:22:23.040 not talking about the old computers. I'm talking about the 0:22:23.080 --> 0:22:25.879 fictional Cathulu gods, the old ones. You have to have 0:22:25.880 --> 0:22:29.320 a computer that size, so large that would rip the 0:22:29.359 --> 0:22:34.040 sanity from your mind. Perhaps less scary, but depends on 0:22:34.080 --> 0:22:36.360 what it's running. Yeah. So I mean this is it's 0:22:36.359 --> 0:22:38.199 sort of again like the I p V six thing. 0:22:38.240 --> 0:22:39.560 This is the kind of thing that's going to get 0:22:39.640 --> 0:22:43.320 us through a long time. We will the the average 0:22:43.359 --> 0:22:45.640 person is not going to need to worry about this 0:22:45.720 --> 0:22:49.840 again anytime. Yeah. Now we say a long time, but 0:22:49.960 --> 0:22:55.480 keep in mind, is computing a long time. Exactly five 0:22:55.560 --> 0:22:58.280 years is a long time in computing terms. I just 0:22:58.280 --> 0:23:00.199 wanted to make that clear before we had people right 0:23:00.240 --> 0:23:03.280