How To Write A Performance Report

how to write a performance report"how to write a performance report"
Server side, Client side?

I have been asked to create a written report for evidence of how server side and client side factors influences a website performance. any one help?

Begin by drawing a line between the two main categories of advanced Web technologies: client-side and server-side technologies. Then talk about what makes them different, and the advantages and disadvantages of each. Then take a stroll through the client-side technologies, providing a plain-English description of what each of them does and a couple of links to where you can learn more. Finally, do very much the same thing for each of the server-side technologies. By the end, you should have a better idea of how it all fits together.

__Waiters and Customers: Clients and Servers__
As mentioned above, advanced Web design technologies may be divided into two broad categories: client-side and server-side. Understanding the difference between the two requires a basic understanding of what goes on when someone views a Web page on the Internet.

You have done it hundreds, if not thousands of times before. You have typed a Web address (URL) into your Web browser’s address field and it has loaded and displayed the corresponding Web page. But what is really going on behind the scenes? In the simplest sense, there are two computers involved in this process: your computer (where your Web browser is running), and the computer somewhere on the Internet (that serves up the Web page in question). In this arrangement, your computer is known as the client and the computer providing the Web page is known as the server. Think of the server as a waiter in a busy restaurant, and the client as one of the customers clamoring for the waiter’s attention. Just like in the real world, one server (or waiter) is responsible for fulfilling the requests of many clients (or customers).

In a busy restaurant, the waiter takes orders from the customers, and then brings them (hopefully) what they ordered. This is surprisingly similar to what goes on between the client and server computers on the Web. The client computer, as you know, runs a Web browser that allows it to view Web pages. This software, when provided with a Web address, sends a request for that address over the Internet to another software program running on the server computer. This program, known as a Web server, responds to that request by sending back the Web page corresponding to the address. It is then up to the browser to interpret that Web page, converting it into human-readable format and slapping it up on the client computer’s screen.

The retrieval and display of any Web page on the Internet proceeds along the same general lines just outlined; however, it is not always quite as simple. Most advances in Web design lately have come with the cost of additional steps in the above process. Whether the additional steps come before or after the waiter hands the customer their order is the difference between client-side and server-side technologies.

In most restaurants, the waiter is not the one responsible for preparing the food; that is the cook’s job. The waiter just takes the order, and relays it to the cook. The cook prepares the order, and then gives it to the waiter to give to the customer. In a way, the cook assists the waiter in his work: giving the customers what they ask for. In the same way, the Web server software running on the server computer can have “helpers” that let it do more than just serve up ready-made Web pages. These helpers are server-side technologies for advanced Web design.

Now, when the customer finally gets their order from the waiter, the logical thing for them to do is eat it, right? But sometimes it is not so simple. Consider, for instance, if the customer ordered pancakes. Typically, they will also be given a little container of maple syrup. If the customer were to just eat their meal as-is, taking a swig of maple syrup after every few bites of pancake, they might get a funny look or two from other patrons at the restaurant. Instead, the customer is expected to spread the syrup on their pancakes before eating it – a small part of the task of preparing the meal has been left for the customer to do. By the same token, some Web pages are more complex for the browser to display than simply taking the HTML and converting it into an image on the screen. Sometimes additional tasks must be completed by the Web browser for the Web page to be displayed. Anything that requires the browser to become a more active participant in determining what to display on the screen is a client-side technology for advanced Web design.

Which is Better?
If, until now, you have mainly dabbled in HTML, you may be asking yourself, “Which is better, client-side or server-side?” While this is a natural question to ask, the fact of the matter is that neither is better than the other. Instead, they each have advantages and disadvantages, and it is up to you to determine which the best choice for any given application.

Client-side technologies such as JavaScript and DHTML tend to be very “nimble” in terms of their abi

How to Write a SQL Server Performance Report - Part 1


how to write a performance report
how to write a performance report
how to write a performance report