Welcome to www.taxkingsandqueens.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.
Finishing a Masterpiece and Getting it on the Shelves (how to get a book published) Writing a book is a monumental task in itself. The process is long, drawn out and grueling. Even if you thoroughly enjoy writing and writing on the same subject for an extended period of time, you will no doubt be exhausted by the writing of a book. Getting that book published, however, will take even more time and effort than producing the thing in the first place. Are you thinking about writing a book? Have you already written one and now are just wondering how to get a book published? If you are, read on. Here are a few tips on how to get from the starting line to triumphantly crossing the finish line. Writing that Book When starting out writing your book, before you are ready to consider how to get a book published, you may already feel daunted. To write a successful book you need to start out with some original thought. You probably have plenty of originality, but you may have trouble getting your ideas into a coherent flow of information that will be digestible by the general public. The first step is to create a book skeleton. You need to organize your thoughts into a progression of chapters. If your book will be non-fiction, start with a table of contents. Write chapter headings and sub-headings. You will automatically know that you’ll need an introductory chapter, but you should probably leave the content of your introduction for the last step. Organize your chapters so that they build upon one another. The more headings that you can brainstorm to begin with, the easier it will be to fill in your book with a series of short articles that flow into one another. If your writing will be fiction, you will need more of a storyboard. You will need to create cause and effect as well as character sketches. To make your story coherent your characters will need events to react to. Their reactions should become predictable as your readers get into the story. You may need to create some situations for your characters just for the purpose of introducing their traits to the reader. These are very general guidelines about how to begin constructing your book. The actual process will be much more involved as you move closer to finding out how to get a book published. Even after you are finished with the bulk of the content, your goal is still a ways off into the future. Getting to Print The next step in how to get a book published is finding a publisher. There are resources at your local library that will let you know who will be the best candidate for publishing the kind of writing that you do. After a series of queries and correspondence with the potential publishers you may get an invitation to send your manuscript. Then the work begins. A publisher is very experienced in finding books that are marketable. He knows what it will take to get your book to sell. Don’t be offended when his editors tears your writing apart. If they are doing that, you can enjoy the fact that you are on the road to a published book. Expect to enter into a close relationship of compromise and change with the editor as you rework and rework what you have already so painstakingly written. When you are finished you will have a readable and clean and correct manuscript ready for print. The road to getting a book published is a long one, but well worth the effort. Trust yourself, and trust the publisher to create a beautiful masterpiece. Don’t be discouraged if several publishers are not interested in your book. You may have to just keep the first few for yourself, and then again, they may eventually get accepted. Good luck and enjoy the process. Web Hosting - The Internet and How It Works In one sense, detailing the statement in the title would require at least a book. In another sense, it can't be fully explained at all, since there's no central authority that designs or implements the highly distributed entity called The Internet. But the basics can certainly be outlined, simply and briefly. And it's in the interest of any novice web site owner to have some idea of how their tree fits into that gigantic forest, full of complex paths, that is called the Internet. The analogy to a forest is not far off. Every computer is a single plant, sometimes a little bush sometimes a mighty tree. A percentage, to be sure, are weeds we could do without. In networking terminology, the individual plants are called 'nodes' and each one has a domain name and IP address. Connecting those nodes are paths. The Internet, taken in total, is just the collection of all those plants and the pieces that allow for their interconnections - all the nodes and the paths between them. Servers and clients (desktop computers, laptops, PDAs, cell phones and more) make up the most visible parts of the Internet. They store information and programs that make the data accessible. But behind the scenes there are vitally important components - both hardware and software - that make the entire mesh possible and useful. Though there's no single central authority, database, or computer that creates the World Wide Web, it's nonetheless true that not all computers are equal. There is a hierarchy. That hierarchy starts with a tree with many branches: the domain system. Designators like .com, .net, .org, and so forth are familiar to everyone now. Those basic names are stored inside a relatively small number of specialized systems maintained by a few non-profit organizations. They form something called the TLD, the Top Level Domains. From there, company networks and others form what are called the Second Level Domains, such as Microsoft.com. That's further sub-divided into www.Microsoft.com which is, technically, a sub-domain but is sometimes mis-named 'a host' or a domain. A host is the name for one specific computer. That host name may or may not be, for example, 'www' and usually isn't. The domain is the name without the 'www' in front. Finally, at the bottom of the pyramid, are the individual hosts (usually servers) that provide actual information and the means to share it. Those hosts (along with other hardware and software that enable communication, such as routers) form a network. The set of all those networks taken together is the physical aspect of the Internet. There are less obvious aspects, too, that are essential. When you click on a URL (Uniform Resource Locator, such as http://www.microsoft.com) on a web page, your browser sends a request through the Internet to connect and get data. That request, and the data that is returned from the request, is divided up into packets (chunks of data wrapped in routing and control information). That's one of the reasons you will often see your web page getting painted on the screen one section at a time. When the packets take too long to get where they're supposed to go, that's a 'timeout'. Suppose you request a set of names that are stored in a database. Those names, let's suppose get stored in order. But the packets they get shoved into for delivery can arrive at your computer in any order. They're then reassembled and displayed. All those packets can be directed to the proper place because they're associated with a specified IP address, a numeric identifier that designates a host (a computer that 'hosts' data). But those numbers are hard to remember and work with, so names are layered on top, the so-called domain names we started out discussing. Imagine the postal system (the Internet). Each home (domain name) has an address (IP address). Those who live in them (programs) send and receive letters (packets). The letters contain news (database data, email messages, images) that's of interest to the residents. The Internet is very much the same. |