The Experts below are selected from a list of 21 Experts worldwide ranked by ideXlab platform

Larry Mcvoy - One of the best experts on this subject based on the ideXlab platform.

  • Hewlett-Packard Laboratories
    2010
    Co-Authors: Carl Staelin, Larry Mcvoy, Bitmover Inc
    Abstract:

    Mhz is a portable ANSI/C program that determines the processor Clock speed in a platform independent way. It measures the execution time of several different C expressions and finds the greatest common divisor to determine the duration of a Single Clock Tick. Mhz can be used by anyone who wants or needs to know the processor Clock speed. In large installations it is often easier to experimentally determine the Clock speed of a given machine than to keep track of each computer. For example, a platform-independent database system optimizer may use the Clock speed while calculating the performance tradeoffs of various optimization techniques. To run the benchmark long enough for timing to be accurate, mhz executes each expression in a loop. To minimize the loop overhead the expression is repeated a hundred times. Unfortunately, repetition enables many hardware and compiler optimizations that can have surprising effects on the experimental results. While writing mhz, much of the intellectual effort went into the design of expressions that minimize the opportunities for compiler and hardware optimization. Mhz utilizes lmbench 2.0’s new timing harness, which manages the benchmarking process. The harness automatically adjusts the benchmark to minimize run time while preserving accuracy, determines the necessary timing duration to get accurate results from the system Clock, and measures and accounts for both loop overhead and measurement overhead. It is used throughout lmbench 2.0 and can be used to measure the performance of other applications.

  • USENIX Annual Technical Conference - mhz: anatomy of a micro-benchmark
    1998
    Co-Authors: Carl Staelin, Larry Mcvoy
    Abstract:

    Mhz is a portable ANSI/C program that determines the processor Clock speed in a platform independent way. It measures the execution time of several different C expressions and finds the greatest common divisor to determine the duration of a Single Clock Tick. Mhz can be used by anyone who wants or needs to know the processor Clock speed. In large installations it is often easier to experimentally determine the Clock speed of a given machine than to keep track of each computer. For example, a platform-independent database system optimizer may use the Clock speed while calculating the performance tradeoffs of various optimization techniques. To run the benchmark long enough for timing to be accurate, mhz executes each expression in a loop. To minimize the loop overhead the expression is repeated a hundred times. Unfortunately, repetition enables many hardware and compiler optimizations that can have surprising effects on the experimental results. While writing mhz, much of the intellectual effort went into the design of expressions that minimize the opportunities for compiler and hardware optimization. Mhz utilizes lmbench 2.0's new timing harness, which manages the benchmarking process. The harness automatically adjusts the benchmark to minimize run time while preserving accuracy, determines the necessary timing duration to get accurate results from the system Clock, and measures and accounts for both loop overhead and measurement overhead. It is used throughout lmbench 2.0 and can be used to measure the performance of other applications.

  • mhz: Anatomy of a micro-benchmark
    1998
    Co-Authors: Carl Staelin, Larry Mcvoy
    Abstract:

    Mhz is a portable ANSI/C program that determines the processor Clock speed in a platform independent way. It measures the execution time of several different C expressions and finds the greatest common divisor to determine the duration of a Single Clock Tick. Mhz can be used by anyone who wants or needs to know the processor Clock speed. In large installations it is often easier to experimentally determine the Clock speed of a given machine than to keep track of each computer. For example, a platform-independent database system optimizer may use the Clock speed while calculating the performance tradeoffs of various optimization techniques. To run the benchmark long enough for timing to be accurate, mhz executes each expression in a loop. To minimize the loop overhead the expression is repeated a hundred times. Unfortunately, repetition enables many hardware and compiler optimizations that can have surprising effects on the experimental results. While writing mhz, much of the intellect..

  • mhz: Anatomy of a micro-benchmark
    USENIX, 1998
    Co-Authors: Carl Staelin, Larry Mcvoy
    Abstract:

    Mhz is a portable ANSI/C program that determines the processor Clock speed in a platform independent way. It measures the execution time of several different C expressions and finds the greatest common divisor to determine the duration of a Single Clock Tick. Mhz can be used by anyone who wants or needs to know the processor Clock speed. In large installations it is often easier to experimentally determine the Clock speed of a given machine than to keep track of each computer. For example, a platform-independent database system optimizer may use the Clock speed while calculating the performance tradeoffs of various optimization techniques. To run the benchmark long enough for timing to be accurate, mhz executes each expression in a loop. To minimize the loop overhead the expression is repeated a hundred times. Unfortunately, repetition enables many hardware and compiler optimizations that can have surprising effects on the experimental results. While writing mhz, much of the intellectual effort went into the design of expressions that minimize the opportunities for compiler and hardware optimization. Mhz utilizes lmbench 2.0’s new timing harness, which manages the benchmarking process. The harness automatically adjusts the benchmark to minimize run time while preserving accuracy, determines the necessary timing duration to get accurate results from the system Clock, and measures and accounts for both loop overhead and measurement overhead. It is used throughout lmbench 2.0 and can be used to measure the performance of other applications.

Carl Staelin - One of the best experts on this subject based on the ideXlab platform.

  • Hewlett-Packard Laboratories
    2010
    Co-Authors: Carl Staelin, Larry Mcvoy, Bitmover Inc
    Abstract:

    Mhz is a portable ANSI/C program that determines the processor Clock speed in a platform independent way. It measures the execution time of several different C expressions and finds the greatest common divisor to determine the duration of a Single Clock Tick. Mhz can be used by anyone who wants or needs to know the processor Clock speed. In large installations it is often easier to experimentally determine the Clock speed of a given machine than to keep track of each computer. For example, a platform-independent database system optimizer may use the Clock speed while calculating the performance tradeoffs of various optimization techniques. To run the benchmark long enough for timing to be accurate, mhz executes each expression in a loop. To minimize the loop overhead the expression is repeated a hundred times. Unfortunately, repetition enables many hardware and compiler optimizations that can have surprising effects on the experimental results. While writing mhz, much of the intellectual effort went into the design of expressions that minimize the opportunities for compiler and hardware optimization. Mhz utilizes lmbench 2.0’s new timing harness, which manages the benchmarking process. The harness automatically adjusts the benchmark to minimize run time while preserving accuracy, determines the necessary timing duration to get accurate results from the system Clock, and measures and accounts for both loop overhead and measurement overhead. It is used throughout lmbench 2.0 and can be used to measure the performance of other applications.

  • USENIX Annual Technical Conference - mhz: anatomy of a micro-benchmark
    1998
    Co-Authors: Carl Staelin, Larry Mcvoy
    Abstract:

    Mhz is a portable ANSI/C program that determines the processor Clock speed in a platform independent way. It measures the execution time of several different C expressions and finds the greatest common divisor to determine the duration of a Single Clock Tick. Mhz can be used by anyone who wants or needs to know the processor Clock speed. In large installations it is often easier to experimentally determine the Clock speed of a given machine than to keep track of each computer. For example, a platform-independent database system optimizer may use the Clock speed while calculating the performance tradeoffs of various optimization techniques. To run the benchmark long enough for timing to be accurate, mhz executes each expression in a loop. To minimize the loop overhead the expression is repeated a hundred times. Unfortunately, repetition enables many hardware and compiler optimizations that can have surprising effects on the experimental results. While writing mhz, much of the intellectual effort went into the design of expressions that minimize the opportunities for compiler and hardware optimization. Mhz utilizes lmbench 2.0's new timing harness, which manages the benchmarking process. The harness automatically adjusts the benchmark to minimize run time while preserving accuracy, determines the necessary timing duration to get accurate results from the system Clock, and measures and accounts for both loop overhead and measurement overhead. It is used throughout lmbench 2.0 and can be used to measure the performance of other applications.

  • mhz: Anatomy of a micro-benchmark
    1998
    Co-Authors: Carl Staelin, Larry Mcvoy
    Abstract:

    Mhz is a portable ANSI/C program that determines the processor Clock speed in a platform independent way. It measures the execution time of several different C expressions and finds the greatest common divisor to determine the duration of a Single Clock Tick. Mhz can be used by anyone who wants or needs to know the processor Clock speed. In large installations it is often easier to experimentally determine the Clock speed of a given machine than to keep track of each computer. For example, a platform-independent database system optimizer may use the Clock speed while calculating the performance tradeoffs of various optimization techniques. To run the benchmark long enough for timing to be accurate, mhz executes each expression in a loop. To minimize the loop overhead the expression is repeated a hundred times. Unfortunately, repetition enables many hardware and compiler optimizations that can have surprising effects on the experimental results. While writing mhz, much of the intellect..

  • mhz: Anatomy of a micro-benchmark
    USENIX, 1998
    Co-Authors: Carl Staelin, Larry Mcvoy
    Abstract:

    Mhz is a portable ANSI/C program that determines the processor Clock speed in a platform independent way. It measures the execution time of several different C expressions and finds the greatest common divisor to determine the duration of a Single Clock Tick. Mhz can be used by anyone who wants or needs to know the processor Clock speed. In large installations it is often easier to experimentally determine the Clock speed of a given machine than to keep track of each computer. For example, a platform-independent database system optimizer may use the Clock speed while calculating the performance tradeoffs of various optimization techniques. To run the benchmark long enough for timing to be accurate, mhz executes each expression in a loop. To minimize the loop overhead the expression is repeated a hundred times. Unfortunately, repetition enables many hardware and compiler optimizations that can have surprising effects on the experimental results. While writing mhz, much of the intellectual effort went into the design of expressions that minimize the opportunities for compiler and hardware optimization. Mhz utilizes lmbench 2.0’s new timing harness, which manages the benchmarking process. The harness automatically adjusts the benchmark to minimize run time while preserving accuracy, determines the necessary timing duration to get accurate results from the system Clock, and measures and accounts for both loop overhead and measurement overhead. It is used throughout lmbench 2.0 and can be used to measure the performance of other applications.

Bitmover Inc - One of the best experts on this subject based on the ideXlab platform.

  • Hewlett-Packard Laboratories
    2010
    Co-Authors: Carl Staelin, Larry Mcvoy, Bitmover Inc
    Abstract:

    Mhz is a portable ANSI/C program that determines the processor Clock speed in a platform independent way. It measures the execution time of several different C expressions and finds the greatest common divisor to determine the duration of a Single Clock Tick. Mhz can be used by anyone who wants or needs to know the processor Clock speed. In large installations it is often easier to experimentally determine the Clock speed of a given machine than to keep track of each computer. For example, a platform-independent database system optimizer may use the Clock speed while calculating the performance tradeoffs of various optimization techniques. To run the benchmark long enough for timing to be accurate, mhz executes each expression in a loop. To minimize the loop overhead the expression is repeated a hundred times. Unfortunately, repetition enables many hardware and compiler optimizations that can have surprising effects on the experimental results. While writing mhz, much of the intellectual effort went into the design of expressions that minimize the opportunities for compiler and hardware optimization. Mhz utilizes lmbench 2.0’s new timing harness, which manages the benchmarking process. The harness automatically adjusts the benchmark to minimize run time while preserving accuracy, determines the necessary timing duration to get accurate results from the system Clock, and measures and accounts for both loop overhead and measurement overhead. It is used throughout lmbench 2.0 and can be used to measure the performance of other applications.

Randall Weis - One of the best experts on this subject based on the ideXlab platform.

  • Temporal Transactions on Single Tables
    Managing Time in Relational Databases, 2010
    Co-Authors: Tom Johnston, Randall Weis
    Abstract:

    This chapter presents a discussion on the maintenance of individual asserted version tables, with focus on temporal entity integrity (TEI). TEI checks insure that, at any given moment of assertion time or during any given period of assertion time, no object may be represented in an effective time Clock Tick more than once. TEI applies to both episodes and to versions within episodes. For episodes, it is the constraint that no two episodes of the same object, in the same period of assertion time, either are contiguous with one another or share even a Single Clock Tick. Using the terminology from Allen relationship taxonomy, it is the constraint that no two episodes of the same object, in the same period of assertion time, either [meet] or [intersect]. They share no Clock Ticks, and they all have at least one unoccupied Clock Tick between them. One is always [before] the other. For versions within an episode, temporal entity integrity is the constraint that each effective-time adjacent pair of versions [meet] but do not [intersect]. They share no Clock Ticks, and have no unoccupied Clock Ticks between them. There are two ways of demonstrating completeness of temporal transactions, including Allen relationship check, and temporal extent transformation completeness check.

Tom Johnston - One of the best experts on this subject based on the ideXlab platform.

  • Temporal Transactions on Single Tables
    Managing Time in Relational Databases, 2010
    Co-Authors: Tom Johnston, Randall Weis
    Abstract:

    This chapter presents a discussion on the maintenance of individual asserted version tables, with focus on temporal entity integrity (TEI). TEI checks insure that, at any given moment of assertion time or during any given period of assertion time, no object may be represented in an effective time Clock Tick more than once. TEI applies to both episodes and to versions within episodes. For episodes, it is the constraint that no two episodes of the same object, in the same period of assertion time, either are contiguous with one another or share even a Single Clock Tick. Using the terminology from Allen relationship taxonomy, it is the constraint that no two episodes of the same object, in the same period of assertion time, either [meet] or [intersect]. They share no Clock Ticks, and they all have at least one unoccupied Clock Tick between them. One is always [before] the other. For versions within an episode, temporal entity integrity is the constraint that each effective-time adjacent pair of versions [meet] but do not [intersect]. They share no Clock Ticks, and have no unoccupied Clock Ticks between them. There are two ways of demonstrating completeness of temporal transactions, including Allen relationship check, and temporal extent transformation completeness check.