• ベストアンサー
  • すぐに回答を!

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。 Nevertheless, it is still, possible to identify some principles of good design that have withstood the test of time and are applicable in a variety of situations. In Section6.2, we will study some common resources, so that the reader can get some intuition in identifying them in real systems. We will then build up, in Section6.3, a set of tool to help us trade freely available (unconstrained) resources for scarce (constrained) ones. Properly applied, these tools allow us to match the design to the constraints at hand. Finally, in Section6.4, we will outline a methodology for performance analysis and tuning. This methodology helps pinpoint problems in a design and build a more efficient and robust system.

noname#111372
noname#111372

共感・応援の気持ちを伝えよう!

  • 英語
  • 回答数3
  • 閲覧数47
  • ありがとう数3

質問者が選んだベストアンサー

  • ベストアンサー
  • 回答No.3
  • bakansky
  • ベストアンサー率48% (3503/7246)

Nevertheless, it is still, possible to identify some principles of good design that have withstood the test of time and are applicable in a variety of situations. とはいえ、評価に耐えてきた設計の要素というものがあり、それを様々な状況において応用することはできる。 In Section6.2, we will study some common resources, so that the reader can get some intuition in identifying them in real systems. セクション 6.2 で、いくつかの共通のリソースを調べてみる。読者はそこから、実際のシステムに応用できるヒントを得ることができるだろう。 We will then build up, in Section6.3, a set of tool to help us trade freely available (unconstrained) resources for scarce (constrained) ones. 次にセクション 6.3 では、制約のあるリソースに代えて自由で有用な(非制約の)リソースを使うためのツールを作ってみよう。 Properly applied, these tools allow us to match the design to the constraints at hand. きちんと適用されるならば、これらのツールは当面の制約下にある設計に応用することができるはずである。 Finally, in Section6.4, we will outline a methodology for performance analysis and tuning. 最後に、セクション 6.4 では、性能解析とチューニングの手法の概略を述べる。 * 余計なお世話かもしれませんが、この文章は大して内容のある文章とは思えません。いわば、本の初めの方に出ている、その本の全体的な流れを説明してある文章のように見えます。こんなものは、わざわざ「翻訳」するほどのものではないような気がします。ざっと目を通しておけば十分なものみたいな印象です。無理に日本語にしなくても、「内容」だけ了解しておけばいいんではないでしょうか。

共感・感謝の気持ちを伝えよう!

その他の回答 (2)

  • 回答No.2

翻訳ソフトでは、こんな感じです。 それにもかかわらず、それは、時間のテストに耐えて、各種の状況で適用可能なよいデザインのいくつかの原則を識別することについて可能なので静かです。 セクション6.2では、私達はいくつかの共通の手段を勉強します。本当のシステムにおいてそれらを識別する時に読者がいくらかの直観を得ることができるように。 私達は、私達が自由な入手可能(無連結式の)の資源を不十分(強制)のものと交換することを手助けするために、セクション6.3でその時ツールのセットを増強します。 適切に、適用されて、これらのツールは、私達によってデザインを制約と手近にマッチさせていることを可能にします。 最後に、セクション6.4では、私達は性能分析と調整のための方法を概説します。 この方法は、デザインのピンポイントの問題、およびより効率的で、頑強なシステムを構築することを助けます。

共感・感謝の気持ちを伝えよう!

  • 回答No.1
  • Tacosan
  • ベストアンサー率23% (3656/15482)

ざっと見た感じでは困るところなどなさそうなんですけど. どこが分からない?

共感・感謝の気持ちを伝えよう!

関連するQ&A

  • 翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイトのコピペはご遠慮ください。 In any system, some resources are less constrained than others. We call the most constrained resource in a system(or the binding constraint) its bottleneck. System performance improves if and only if we devote additional resources to a bottlenecked resource. Conversely, decreasing the amount of an unconstrained resource does not adversely affect performance. When we relieve one bottleneck, however, it is possible for another resource to become a bottleneck. Thus, we must remove the bottlenecks one by one until all the resources are equally constrained. We call such a system a balanced system. A balanced system is optimal, in that we fully utilize every component. However, in practice, we rarely achieve balanced systems. Rapid changes in technology, market constraints, and customer expectations mean that a system's components are almost constantly in flux, with the bottleneck moving from place to place in the system.

  • 翻訳をお願いしたいです。コンピューター関係の書物の文章です。

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 We call a freely available resource an unconstrained resource, and a resource whose availability determines overall system performance a constrained resource. In this system, the link's bandwidth constrains the overall performance, as measured by the effective throughput of the link. This, therefore, is the constrained resource. In this example, the computer’s processing speed and money size are unconstrained resources.

  • 翻訳をお願いしたいです。コンピューター関係の書物の文章です。

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 A system designer must typically optimize one or more performance metrics given a set of resource constrains. A performance metric measures some aspect of a system's performance, such as throughput, response time, cost development time, or mean time between failures(we will define these metrics more formally in Section 6.2). A resource constraint is a limitation on a resource, such as time, bandwidth, or computing power, that the design must obey.

  • 翻訳をお願いしたいです。コンピューター関係の書物の文章です。

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 Besides constraints on these five resources, two major constraints are purely social :standards and market requirements. ・Standard force the design to conform to some widely agreed-upon requirements that may or may not be appropriate for that particular design. Though standards are essential to allow interoperability and can reduce costs by promoting competition, poorly designed standards severely restrict the design space. Worse yet, an underspecified standard may lead to faulty implementations that are not even interoperable. A good example of a bad standard is the Q.2931 standard for signaling in ATM networks. The standard is unnecessarily complex, and therefore hard to implement and hard to modify. Yet, to succeed in the marketplace, switch manufacturers have to obey it, thus slowing the rate at which ATM networks spread. ・Market requirements, like poorly designed standards, are unfortunate realities. A company may decide that products being designed must be backward-compatible with a previous product, or that they must use a particular operating system, or that they must support some set of standards. These essentially political decisions set the framework for a design. Market requirements may also determine the amount of human effort that can be expended on a design project. It is remarkable how much time is spent on building graphical user interfaces, sometimes at the expense of the system underlying the interface!

  • 翻訳をお願いしたいです。コンピューター関係の書物の文章です。

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 In any system, some resources are more freely available than others. For example, consider a high-end personal computer connected to the Internet with a 28.8-Kbps modem. In this system, for tasks that require only a moderate amount of processing, such as reading email, the rate at which the computer can process information far exceeds the capacity of the transmission link.

  • 翻訳をお願いしたいです。コンピューター関係の書物の文章です。

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 If we could quantify and control every aspect of a system, then system design would be a relatively simple matter. Unfortunately there are several practical reasons why system design is both an art and a science. First, although we can quantitatively measure some aspects of system performance, such as throughput or response time, we cannot measure others, such as simplicity, scalability, modularity, and elegance. Yet a designer must make a series of trade- offs among these intangible quantities, appealing as much to good sense and personal choice as performance measurements. Second, rapid technological change can make constraint assumptions obsolete. A designer must not only meet the current set of design constraints, but also anticipate how future changes in technology might affect the design. The future is hard to predict, and a designer must appeal to instinct and intuition to make a design "future-proof." Third, market conditions may dictate that design requirements change when part of the design is already complete. Finally, international standards, which themselves change over time, may impose irksome and arbitrary constraints. These factors imply that, in real life, a designer is usually confronted with a complex, underspecified, multifactor optimization problem. In the face of these uncertainties, prescribing the one true path to system design is impossible.

  • 翻訳をお願いしたいです。コンピューター関係の書物の文章です。

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 By explicitly identifying performance metrics and resource constraints, a system designer ensures that the design space is well defined, the solution is feasible, and the design is efficient. She can then trade unconstrained resources for constrained ones to maximize the design's utility at the least cost. Continuing with our example, a system designer might use the PC's surplus computational power to compress data as much as possible, to best exploit the limited capacity of the transmission link. A well-designed system maximizes achievable performance while still satisfying the resource constraints.

  • 卒論に使用するため、翻訳をお願いしたいです。コンピューター関係の書物の

    卒論に使用するため、翻訳をお願いしたいです。コンピューター関係の書物の文章です。 We call the mean time to complete a task its response time and the mean number of tasks that can be completed in a unit time the throughput. There is an important relationship between throughput and response time that we will use often in this book: the mean number of concurrent activities in a system, also called its degree of parallelism, is the product of the throughput and the response time.

  • 翻訳をお願いしたいです。コンピューター関係の書物の文章です。

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 Consider a building that has two floors, with an escalator to carry people from one floor to the other. Ignoring queuing delays, the response time for a passenger is the mean time taken by the escalator to ascend or descend one floor. The throughput (bandwidth) is the mean number of passengers that can be loaded or per second. Suppose that an average of five people step on the escalator in one second, and that the escalator takes an average of 10 seconds to go up one floor. The response time for a passenger, therefore, is 10 seconds, and the throughput of the escalator is 5 passengers/second. Thus, the degree of parallelism, which is the mean number of passengers carried simultaneously, is 5*10=50. To see this, mark a passenger with a daub of red paint as she steps on the escalator. In the ten seconds that she takes to reach the top, we expect that fifty more passengers boarded the escalator. Thus, when she steps off, the escalator carries an average of fifty passengers, which is its degree of parallelism.

  • 卒論に使用するため、翻訳をお願いしたいです。コンピューター関係の書物の

    卒論に使用するため、翻訳をお願いしたいです。コンピューター関係の書物の文章です。 We can describe most computer system resources as a combination of five common resources: time, space, computation, money, and labor. We now study these resources in more detail, with examples of how they arise in real-world problems, and a description of associated performance metrics. Our definitions of these resources are purposely vague, since the exact definition varies with the problem.