255.vortex Benchmark

Origin: 
  SPEC INT 2000

Syntax for running:
  vortex <file>.raw

Note:  The <file>.raw reads several other files.  Be sure the paths 
are set correctly in the .raw file

The input directory (under this directory) contains sample input files.  
These input files and their size are as follows:


Input	Simulation Size (number of instructions at o0)
-----	---------------
ref1	168.6 billion
ref2    191.2 billion  
ref3    188.2 billion  
train   24 billion 
test    13 billion 
lgred   1510 million
mdred	 547 million
smred	 113 million


Benchmark Authors:
  Peter R. Homan
 
Benchmark Program General Category: 
  Database
 
Benchmark Description: 

  VORTEx is a single-user object-oriented database transaction benchmark
  which which exercises a system kernel coded in integer C.  The VORTEx
  benchmark is a derivative of a full OODBMS that has been customized to
  conform to SPEC CINT2000 (component measurement) guidelines.

  The benchmark 255.vortex is a subset of a full object oriented database
  program called VORTEx.  (VORTEx stands for "Virtual Object Runtime
  EXpository.")

  Transactions to and from the database are translated though a schema.  (A
  schema provides the necessary information to generate the mapping of the
  internally stored data block to a model viewable in the context of the
  application.)


Input Description: 

  The schema as provided with the benchmark is pre-configured to manipulate
  three different databases:  mailing list, parts list, and geometric data.
  Both little-endian and big-endian binaries for the schema are provided.

  The benchmark builds and manipulates three separate, but inter-related
  databases based on the schema.  The size of the database is scalable, and
  for CINT2000 guidelines has been restricted to about 200 Mbytes.

  VORTEx been modified to not commit transactions to memory in order to
  remove input-output activity from this CINT2000 (component) benchmark.

  The workload of VORTEx has been modeled after common object-oriented
  database benchmarks with modifications to vary the mix of transactions.

  The 255.vortex benchmark is run three different times, each time a
  different mix of database inserts, deletes and lookups is used to
  simulate different database usage patterns.


Output Description: 

  The benchmark 255.vortex is run using a workload simulating different 
  dataset sizes and access patterns.  Each run produces one output file.  
  Each output file is a log of all transactions occurring during the
  running of the benchmark, these transactions include creating entries in
  the database, deleting entries, and entry lookups.

Reference:
     http://www.vortex01.com

