外文翻譯--網(wǎng)絡(luò)性能的測(cè)量(文件)
【正文】 of the work drivers is truly awful and is only getting 10 percent of the performance of the board. 網(wǎng)絡(luò)性能的測(cè)量 當(dāng)一個(gè)網(wǎng)絡(luò)的運(yùn)行效果很差的時(shí)候，它的用戶通常會(huì)向網(wǎng)絡(luò)運(yùn)行商抱怨并要求提高網(wǎng)絡(luò)的質(zhì)量。中文 2100 字 英文翻譯：出自《 Computer Network》第四版 Andrew 著 Network Performance Measurement When a work performs poorly, its users often plain to the folks running it, demanding improvements. To improve the performance, the operators must first determine exactly what is going on. To find out what is really happening, the operators must make measurements. In this section we will look at work performance measurements. The discussion below is based on the work of Mogul (1993). The basic loop used to improve work performance contains the following steps: 1. Measure the relevant work parameters and performance. 2. Try to understand what is going on. 3. Change one parameter. These steps are repeated until the performance is good enough or it is clear that the last drop of improvement has been squeezed out. Measurements can be made in many ways and at many locations (both physically and in the protocol stack). The most basic kind of measurement is to start a timer when beginning some activity and see how long that activity takes. For example, knowing how long it takes for a TPDU to be acknowledged is a key measurement. Other measurements are made with counters that record how often some event has happened (., number of lost TPDUS). Finally, one is often interested in knowing the amount of something, such as the number of bytes processed in a certain time interval. Measuring work performance and parameters has many potential pitfalls. Below we list a few of them. Any systematic attempt to measure work performance should be ca
畢業(yè)設(shè)計(jì)相關(guān)推薦
鄂ICP備17016276號(hào)-1