We will be undergoing scheduled maintenance on May 20th, 2013 at 02:00 GMT.
MySQL 5 Administration-Part 1 Tutorials
Architecture / Hardware and OS Issues
Subtitles of the Movie (MySQL 5 Administration-Part 1 / Architecture / Hardware and OS Issues)
We can't have a thorough discussion about the MySQL server without also including in that discussion a little talk about the hardware that, that server software is going to run on and for that matter the operating system that, that server software is going to run on. So let's take a little time and discuss these issues as well. Just lightly for right now we'll probably get into it a little bit more later. We have choices to make in hardware. We always have had but we've got more choices I think than, than ever these days. One thing is we need to think about do we want to be running on 32-bit or 64-bit hardware? A 64-bit's going to be more expensive, it's also going to be more capable perhaps. If we're running in a 32-bit system then we have a number of address limits at around 4 gigabytes or so because that's the biggest number that we can generate is 4 billion plus to specify an address location. That's an address location inside of a file as well as an address location in RAM. So a 32-bit system limits us in a number of different ways. On the other hand we have to be careful that we if we get 64-bit hardware that we also have a 64-bit operating system running on that hardware and we don't want to trust this the configuration of the hardware when in fact the software needs to run in the operating system. So if we try to put a 64-bit version of MySQL on a 64-bit machine but one that's running a 32-bit operating system, we just lost. It's not going to work for us too well. So if we're going to use 64-bit hardware and to get access to all 64 of those bits for our processing, then we need to also make sure that we have a 64-bit operating system. Plenty of them out there they're nice and stable these days so go for it. Another question is do we want to stick with a physical server or do we want to use a virtual server? There really is no clear winner these days because the physical hardware is getting to be so fast as well. So doing things on a virtual server may not necessarily give us an advantage as it once might have. The idea of multiple cores and multiple processors also comes up. MySQL server can take advantage of multiple cores and multiple processors. However, each thread exists in only one core someplace. So it can't go multi-core for the thread. But that's okay as long as we can have multiple cores being used to advantage with different threads, then that's great. That allows us to do more things. While we're going out there shopping for hardware, probably a good idea to find a system that has battery backup. As a matter of fact that flows all the power through the battery so there is no even millisecond delay while we're dropping into using the battery alone. And we would like to have something where an optional generator would kick in in case the power goes down so that we can keep on running, that would be really nice. In addition to just the iron that we're going to run these things on, our storage choices are also kind of varied and we have to make some decisions there. So just like going clothes shopping for a young kid, for our MySQL server we not only have to think about what data size do we have right now but what data size do we expect it to be within a reasonable period of time. How much do we expect it to grow in that time so that we can plan for that expansion and not suddenly find ourselves desperately in need of more disk space before the next person submits an order. How much concurrent traffic do we expect? Do we expect to have like five or six people on the system or a time or 5 or 6, 000 people at a time? That will make a difference also in the storage media that we get. How quickly can we read and write on this storage media? That's really important. Generally having a sand system or a RAID of some kind are going to be good choices these days because we also want to have redundancy of this storage on the production system. So Sands and RAIDS are both really good choices for us, battery backed drives again are really good. If the power does go down even momentarily, it's nice to have that battery back drive so that it can do that last little write before the whole thing goes down. Nothing worse than having things almost written and then be lost because of momentary power fluctuation. So battery back drive is a good thing to have. All kinds of choices here, this is just scratching the surface of them but I just wanted to make you aware that we can't just focus on the software, we have to focus on where the software is going to live as well. Okay. In the next chapter we're going to talk some more about hardware but more about the resources that the MySQL server uses. And some of that will be hardware related and much of that will be software related. But RAM allocations, where things are stored on disk, all of that stuff enters into how MySQL uses resources. That's going to be the subject of the next chapter.
Tutorial Information
| Course: | MySQL 5 Administration-Part 1 |
| Author: | David Swain |
| SKU: | 34307 |
| ISBN: | 978-1-61866-086-2 |
| Release Date: | 2012-12-31 |
| Duration: | 16 hrs / 171 lessons |
| Work Files: |
Yes |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |
VTC Sign up & Benefits
- Unlimited Access
- 81,350 Video Tutorials (14,200 free)
- Video Available as Flash or QuickTime
- Over 715 Courses
- $30 for One Month Access
- Multi-User Discounts Available
