Welcome to www.pinayjade.com
|
Web Hosting - Bandwidth and Server Load, What's That?
Two key performance metrics will impact every web site owner sooner or later: bandwidth and server load.
Bandwidth is the amount of network capacity available, and the term actually covers two different aspects. 'Bandwidth' can mean the measure of network capacity for web traffic back and forth at a given time. Or, it sometimes is used to mean the amount that is allowed for some interval, such as one month. Both are important.
As files are transferred, emails sent and received, and web pages accessed, network bandwidth is being used. If you want to send water through a pipe, you have to have a pipe. Those pipes can vary in size and the amount of water going through them at any time can also vary.
Total monthly bandwidth is a cap that hosting companies place on sites in order to share fairly a limited resource. Companies monitor sites in order to keep one site from accidentally or deliberately consuming all the network capacity. Similar considerations apply to instantaneous bandwidth, though companies usually have such large network 'pipes' that it's much less common for heavy use by one user to be a problem.
Server load is a more generic concept.
It often refers, in more technical discussions, solely to CPU utilization. The CPU (central processing unit) is the component in a computer that processes instructions from programs, ordering memory to be used a certain way, moving files from one place to the next and more.
Every function you perform consumes some CPU and its role is so central (hence the name) that it has come to be used as a synonym for the computer itself. People point to their case and say 'That is the CPU'. But, the computer actually has memory, disk drive(s) and several other features required in order to do its job.
Server load refers, in more general circumstances, to the amount of use of each of those other components in total.
Disk drives can be busy fetching files which they do in pieces, which are then assembled in memory and presented on the monitor, all controlled by instructions managed by the CPU.
Memory capacity is limited. It's often the case that not all programs can use as much as they need at the same time. Special operating system routines control who gets how much, when and for how long, sharing the total 'pool' among competing processes.
So, how 'loaded' the server is at any given time or over time is a matter of how heavily used any one, or all, of these components are.
Why should you care?
Because every web site owner will want to understand why a server becomes slow or unresponsive, and be able to optimize their use of it.
When you share a server with other sites, which is extremely common, the traffic other sites receive creates load on the server that can affect your site. There's a limited amount you can do to influence that situation. But if you're aware of it, you can request the company move you to a less heavily loaded server. Or, if the other site (which you generally have no visibility to) is misbehaving, it's possible to get them moved or banned.
But when you have a dedicated server, you have much more control over load issues. You can optimize your own site's HTML pages and programs, tune a database and carry out other activities that maximize throughput. Your users will see that as quicker page accesses and a more enjoyable user experience.
Web Hosting - Redundancy and Failover Among the more useful innovations in computing, actually invented decades ago, are the twin ideas of redundancy and failover. These fancy words name very common sense concepts. When one computer (or part) fails, switch to another. Doing that seamlessly and quickly versus slowly with disruption defines one difference between good hosting and bad. Network redundancy is the most widely used example. The Internet is just that, an inter-connected set of networks. Between and within networks are paths that make possible page requests, file transfers and data movement from one spot (called a 'node') to the next. If you have two or more paths between a user's computer and the server, one becoming unavailable is not much of a problem. Closing one street is not so bad, if you can drive down another just as easily. Of course, there's the catch: 'just as easily'. When one path fails, the total load (the amount of data requested and by how many within what time frame) doesn't change. Now the same number of 'cars' are using fewer 'roads'. That can lead to traffic jams. A very different, but related, phenomenon occurs when there suddenly become more 'cars', as happens in a massively widespread virus attack, for example. Then, a large number of useless and destructive programs are running around flooding the network. Making the situation worse, at a certain point, parts of the networks may shut down to prevent further spread, producing more 'cars' on now-fewer 'roads'. A related form of redundancy and failover can be carried out with servers, which are in essence the 'end-nodes' of a network path. Servers can fail because of a hard drive failure, motherboard overheating, memory malfunction, operating system bug, web server software overload or any of a hundred other causes. Whatever the cause, when two or more servers are configured so that another can take up the slack from one that's failed, that is redundancy. That is more difficult to achieve than network redundancy, but it is still very common. Not as common as it should be, since many times a failed server is just re-booted or replaced or repaired with another piece of hardware. But, more sophisticated web hosting companies will have such redundancy in place. And that's one lesson for anyone considering which web hosting company may offer superior service over another (similarly priced) company. Look at which company can offer competent assistance when things fail, as they always do sooner or later. One company may have a habit of simply re-booting. Others may have redundant disk arrays. Hardware containing multiple disk drives to which the server has access allows for one or more drives to fail without bringing the system down. The failed drive is replaced and no one but the administrator is even aware there was a problem. Still other companies may have still more sophisticated systems in place. Failover servers that take up the load of a crashed computer, without the end-user seeing anything are possible. In fact, in better installations, they're the norm. When they're in place, the user has at most only to refresh his or her browser and, bingo, everything is fine. The more a web site owner knows about redundancy and failover, the better he or she can understand why things go wrong, and what options are available when they do. That knowledge can lead to better choices for a better web site experience. Job Hunt Challenges for the Over 50 Crowd If you have just recently lost a job or maybe are not happy with the job you are currently holding, you are going to be on the hunt for a new job. Hunting for new job is never easy, whether it is your first or your tenth job. You know that it takes a good amount of preparation till you might hold another permanent job. But for the older crowd, especially the crowd over fifty, the challenge of finding a new job is even greater. Explore some of the facts why it is more challenging to find a job after 50. Starting out by the age factor, many companies want young and dynamic employees that are open to new and challenging tasks. Many employers believe that a person over 50 is set in his or her ways and therefore not able to tackle the same great tasks that might open up as a young, fresh out of college open minded person. A person over 50 is closer to retirement and might not want to take any risks as a young career fresh from school employee. Risks are sometimes what a company needs to get forward, new ideas, new thinking. Another reason is the salary competition. If you are over 50 and looking for another job, you most likely have a lot of experience in you sector. Experience usually is measured in money and the salary for an experienced person is generally higher than a starter salary. While experience is desired, some companies can just not afford to hire somebody for 10-20 thousand dollars more than they can get the fresh from college employee. If you lost your job, you might accept one of the lower salaries, but while you are in the application process, the human resource person reading your résumé does not have that information about you. Some of the bigger companies get scared by the fact that you are really close to retirement and if there are certain retirement plans and structure in place at a company, they might not want to hire you. You could retire within 10-15 years or less and then the company is stuck with paying you retirement payments. Hiring a younger person instead guarantees them no retirement payments or plans for retirement in general for the next 20-30 years. From the employer’s side, these are great savings for their pocket. Another reason often seen from employers as a reason not to hire a person over 50 is that the person they are hiring might be more prone to sickness and take more sick days than a young person. Why would they think that? Statistics have shown them that the tendency for time off due to sickness is greater for people crossing the age threshold of 50 years versus younger people. Be honest, being over 50 means for most people more aches and pains all over the body. You are more tired and get exhausted quicker. So if you do get a chance to go to an interview when looking for a new job, you need to make the best out of it. Besides all the factors mentioned above, a person that is over 50 and is looking for a job can be a great addition to any company and you need to make sure that you let your interviewer know that. An interview is a great challenge and can be mastered quite well if keeping these thoughts that employers have in mind. Emphasize the fact that you do bring experience and connections. Let them know that if they hire you, they get a person that at least is settled in life. You have had all your children, or did not want any, but at least you will not be missing because of pregnancy, birth of a child, and sickness of a young child or similar events. |