Throughput. Up to 50 Mbps per CPE
Throughput. Transmission and reception throughput is determined by a myriad of factors, such as, but not limited to, weather, time of day, condition of the network, third party services, number of Subscribers using the Service, usage by emergency services, characteristics of the subscriber’s equipment, geographical location, building characteristics and various obstructions to the wireless signal. Transmission and reception rates published in the Provider’s Service plans are targets that should be typically obtainable but are not guaranteed. Access locations may be removed and or updated from time to time in the Provider’s sole discretion and actual coverage, locations and quality may vary. Wireless access is subject to unavailability, including, but not limited to, unavailability for emergencies, colocation failures, maintenance, and transmission limitations. Network speeds for access may vary. Access may be based on third party networks over which the Provider has no control beyond contractual service level agreements, if any, with the third party network provider. The Provider may, but is not required to, modify the 802.11x standard. Wireless access is transmitted over complex unpredictable networks. Not all Internet Sites can be accessed and you may receive an error message if you attempt to access a site that cannot be accessed.
Throughput. (a) Throughput Commitment and Terminalling Service Fee. Customer shall deliver and/or pay for the Minimum Throughput Commitment at the Terminal, and TLO shall make available to Customer at all times commingled storage and throughput capacity at the Terminal sufficient to allow Customer to throughput the Reserved Capacity. Customer shall pay the Terminalling Service Fee for such service as set forth in a Terminal Service Order. Allocation of storage and throughput capacity for separate Products at the Terminal shall be set forth in a Terminal Service Order, if applicable. TLO shall not make any commitments to third parties that would interfere with the ability of Customer to throughput the Reserved Capacity. Customer commits to deliver and/or pay for the Minimum Throughput Commitment on a Monthly basis during the Term.
Throughput. The throughput of an IP service is a measure that applies to a particular pair of source and destination IP address. It is defined in two variants: the IP Packet Throughput (IPPT) and the Octet based IP Packet Throughput (IPOT). The IPPT indicates the number of packets per second the service can handle, and the IPOT indicates the accumulated number of octets in those packets that the service can handle. About the SLA parameter throughput the following observations apply: • Throughput is important. Example: a video stream is defined at 1 MBit, and only useful at 1 MBit. At 0.9 MBit, it cannot be displayed. Another: company wants to synchronize its various data bases outside business hours, not during peak sales hours. • In case of different service classes, throughput applies for each individual service class, and can be different per class. • The parameters also depend on source address and/or destination address (differences between local traffic, long-distance traffic etc.). In this aspect the model of the network infra- structure as a set of ‘pipes’ with QoS attributes becomes evident. • Service Throughput can depend on time of day/day of week etc. Either the value for this param- eter applies always (also in peak hour), or there might be different values for different times (inside or outside business hours).
Throughput the Customer’s Bandwidth Profile identified in the Agreement. and, while the Supplier will use commercially reasonable efforts to achieve the Supplier’s Service Level Objectives, the Supplier shall not have any liability to the Customer should the Supplier fail to achieve any of the Service Level Objectives.
Throughput. Normal Maximum Raffinate Flow (Ton/Ton P2O5) (*****) (*****) EXHIBIT G Raffinate calculations Total Raffinate Charge, $ per ton (*****) A = Actual delivered rock cost per ton in dollars as P2O5 times (x) the current consumption of Phosphate Rock to produce one net ton of (****) P2O5.
Throughput. Prices in Table 1 are inclusive of worldwide throughput at the Worldspan Host complex, but only for transmissions associated with connections specifically identified in Table 1. TABLE 1 – IP VPN and Managed DSL Country IP VPN 64K (includes CS 805 router) IP VPN 128K (includes CS 2610XM router) IP VPN 256K (includes CS 2610XM router) IP VPN 1024K (includes CS 2610XM router) IP VPN 2048K (includes CS 2610XM router) Managed DSL 32K Internet 32K Intranet (includes CS 827 router) Australia $ [**] $ [**] $ [**] $ [**] $ [**] Austria $ [**] $ [**] $ [**] $ [**] $ [**] Belgium $ [**] $ [**] $ [**] $ [**] $ [**] $ [**] China $ [**] $ [**] $ [**] $ [**] $ [**] Czech $ [**] $ [**] $ [**] $ [**] $ [**] Denmark $ [**] $ [**] $ [**] $ [**] $ [**] Egypt * $ [**] $ [**] $ [**] $ [**] $ [**] Finland $ [**] $ [**] $ [**] $ [**] $ [**] France $ [**] $ [**] $ [**] $ [**] $ [**] $ [**] Germany $ [**] $ [**] $ [**] $ [**] $ [**] $ [**] Greece $ [**] $ [**] $ [**] $ [**] $ [**] [**] = Confidential treatment requested for redacted portion; redacted portion has been filed separately with the Commission. Country IP VPN 64K (includes CS 805 router) IP VPN 128K (includes CS 2610XM router) IP VPN 256K (includes CS 2610XM router) IP VPN 1024K (includes CS 2610XM router) IP VPN 2048K (includes CS 2610XM router) Managed DSL 32K Internet 32K Intranet (includes CS 827 router) Guam* $ [**] $ [**] $ [**] $ [**] $ [**] Hong Kong $ [**] $ [**] $ [**] $ [**] $ [**] $ [**] Hungary $ [**] $ [**] $ [**] $ [**] $ [**] India $ [**] $ [**] $ [**] $ [**] $ [**] Ireland $ [**] $ [**] $ [**] $ [**] $ [**] Israel $ [**] $ [**] $ [**] $ [**] $ [**] Italy $ [**] $ [**] $ [**] $ [**] $ [**] $ [**] Japan $ [**] $ [**] $ [**] $ [**] $ [**] Korea $ [**] $ [**] $ [**] $ [**] $ [**] Malta $ [**] $ [**] $ [**] $ [**] $ [**] Xxxxxxxx Islands $ [**] $ [**] $ [**] $ [**] $ [**] Morocco* $ [**] $ [**] $ [**] $ [**] $ [**] Netherlands $ [**] $ [**] $ [**] $ [**] $ [**] $ [**] N. Mariana Islands $ [**] $ [**] $ [**] $ [**] $ [**] Norway $ [**] $ [**] $ [**] $ [**] $ [**] Poland $ [**] $ [**] $ [**] $ [**] $ [**] Portugal $ [**] $ [**] $ [**] $ [**] $ [**] Romania $ [**] $ [**] $ [**] $ [**] $ [**] Saudi Arabia* $ [**] $ [**] $ [**] $ [**] $ [**] Singapore $ [**] $ [**] $ [**] $ [**] $ [**] South Africa* $ [**] $ [**] $ [**] $ [**] $ [**] Spain $ [**] $ [**] $ [**] $ [**] $ [**] $ [**] Sweden $ [**] $ [**] $ [**] $ [**] $ [**] Switzerland $ [**] $ [**] $ [**] $ [**] $ [**] Turkey $ [**] $ [**] $ [**] $ [**] $ [**] Ukrai...
Throughput. The data transfer rates detected for the selected volume over the selected time range. • Volume. The name of the selected volume and its alarm state. Virtual switch monitoring A Hyper-V Virtual Switch is a software-based layer-2 Ethernet network switch. The switch connects virtual machines to virtual and physical networks. To review data collected about a specific volume or all volumes, make your selection in the Quick-View. • Virtual Switches view on page 94 • Summary - All Virtual Switches view on page 95 • Summary - Virtual Switch view on page 97 • Virtual Switch Topology view on page 100 Virtual Switches view The Virtual Switches tree view lists the available volumes and indicates their severity state. This view appears in the Quick-View on the left when you select the Virtual Switches tile in the Virtual Environment view. Figure 130. Virtual Switches view Selecting the All Virtual Switches node displays the overall resource utilization for all virtual switches in your integrated system and identifies the ones that consume the highest amount of network resources in the Summary - All Virtual Switches view on the right. Similarly, selecting a virtual switch node shows switch-specific metrics in the Summary - Virtual Switch view. Table 80. Description of the View Data displayed • Alarm severity. The state of the most recent alarm raised against the virtual switch. • All Volumes. A parent node for the instances of all virtual switches that appear in this view. • Volume. The name of the virtual switch. Where to go next Drill down on: • All Volumes. Shows the Summary - All Virtual Switches view in the Quick-View. • Volume. Shows the Summary - Virtual Switch view in the Quick-View. Summary - All Virtual Switches view The Summary - All Virtual Switches view displays overall resource utilization information for a group of virtual switches and identifies the ones that consume the highest amounts of system resources, potentially causing performance bottlenecks. This view appears in the Quick-View on the left when you select All Virtual Switches in the Virtual Environment view. Figure 131. Summary - All Virtual Switches view This view is made up of the following embedded views: • Alarms • Top Bandwidth Consumers • The Highest Number of Ports • Top Overall Utilization • Top Packets per Second Table 81. Alarms Description Lists the alarms generated against the monitored virtual switches. Data displayed • Alarm Message. An explanation about why the alarm occurred. •...
Throughput. Changes in vehicular and person throughput will be examined to assess the extent to which congestion was reduced. According to NCHRP’s Guide to Effective Freeway Performance Measurement, throughput is a fundamental measure of freeway performance. Throughput is a measure of the number of users “served” by transportation system. The congestion analysis focuses on how deploying the UPA projects in the SR 520 corridor changed the throughput in the systems (roadways and transit) serving commuters over Lake Washington. The basic premise for using throughput as a performance measure is that the UPA projects reduced congestion in the corridor because more vehicles and/or persons were “serviced” after the improvements, even if the travel time or travel time reliability performance measures show no change. Table 4-3 shows the hypotheses, measures and performance and data needed for investigating the effects of the Seattle/LWC UPA projects on throughput. Vehicle throughput (VT) will be determined by counting the number of vehicles using SR 520 and other alternate routes around Lake Washington. Vehicle throughput will be derived from WSDOT’s Traffic System Management detector station data. The roadway segments on which vehicle throughput will be assessed include the following: SR 520 (between I-5 and I-405) SR 520 (between Issaquah/MP 19.41 and I-405) I-90 (between I-5 and I-405) – both general purpose and express lanes I-90 (between SR 202 and I-405) SR 522 (between I-405 and I-5) I-5 (between SR 522 and I-405) I-405 (between SR 167 and SR 522). Person throughput (PT) will also be used to assess the degree to which the UPA projects impacted congestion on the SR 520 corridor. Person throughput is the total number of persons “served” by the different modes of travel that utilize the SR 520 corridor. For the Seattle/LWC UPA projects, the total person throughput can be estimated by summing the following: PT changes attributed to transit projects PT changes attributed to TDM projects PT changes attributed to SR 520 tolling PT changes attributed to the technology projects. PT will be estimated by multiplying the VT for different vehicle classes by the average number of occupants per vehicles per class. Vehicle-miles traveled (VMT) and Person-xxxxx traveled (PMT) will also be computed. VMT is the product of the number of vehicles traveling over a length of facility (VT) by the length of the facility, while PMT is the product of the number of persons us...
Throughput. Customer shall be responsible for the function and throughput of all Customer Provided Equipment. Williams Communications will providx xxxxxxnmentally controlled facilities suitable for operation of Customer Provided Equipment which is located at Williams Communications' premises. Xxxxxxxx shall provide reasonable axxxxxxxxe in restoral of Customer-Provided Equipment at the Teleport.
