| Evaluation seq. num.
|| For the first evaluation leave this field at "1"
|Evaluator-IDfirstname.lastname@example.org|| Unique ID of the evaluator that carried out this specific evaluator.
|Evaluation describtion||text|| The web archiving team at the Austrian National Library produces information about the content of a web archive during the harvesting process. The result is stored as huge text files.
Each line of the log holds the meta data of one object.
The application reads the file content line by line, extract the mime type “item 10 (Subtype)” and count all occurrences.
Goal / Sub-goal:
Performance efficiency / Throughput
) The processing of these text files is very time consuming and needs parallelized processing
) The workflow uses text files produced by the web crawler
) The hadoop split size has been 64MB (the default value)
) The result has been measured as GB/min/platform
Reliability / Stability Indicators
) No external tools are used
) The processing application has been implemented as a JAVA JAR map / reduce application
) All needed components (program logic, Hadoop method implementations, dependencies) are integrated
) The result has been measured "manually" and reflected as a boolean value (true = met the requirements)
Reliability / Runtime stability
) Use Hadoop admin interface to identify failed tasks.
) Use Hadoops output to identify dropped records / any reported errors.
) The result has been measured as an integer value reflecting the number of identified run time failures.
| Textual description of the evaluation and the overall goals
|Evaluation-Date||DD/MM/YY||20/08/12|| Date of evaluation
||Platform ONB 1|| Unique ID of the platform involved in the particular evaluation - see Platform page included below
|| Austrian National Library - Web Archive
|| Link to dataset page(s) on WIKI
|Workflow method|| string
|| Hadoop map / reduce application implemented in JAVA (jar).
|| Taverna / Commandline / Direct hadoop etc...
| Workflow(s) involved
|| Link(s) to MyExperiment if applicable
| Tool(s) involved
||URL(s)|| Link(s) to distinct versions of specific components/tools in the component registry if applicable
|Link(s) to Scenario(s)|| URL(s)
|| Link(s) to scenario(s) if applicable
|Platform-ID||String|| ONB 1
|| Unique string that identifies this specific platform.
Use the platform name
|Platform description||String|| Experimental cluster (setup 06.2012).
8 (HT) cores per node. Using max. 7 cores for map / reduce slots (one for the OS).
Map / reduce slots ratio 6 / 1.
|Human readable description of the platform. Where is it located, contact info, etc.|
|Number of nodes||integer||5|| Number of hosts involved - could be both physical hosts as well as virtual hosts
|Total number of physical CPUs||integer||5|| Number of CPU's involved
|CPU specs||string||Xeon X3440@2.53GHz Quadcore CPU|| Specification of CPUs
|Total number of CPU-cores||integer|| 40 Cores (5 * 8 Cores)
|| Number of CPU-cores involved (4 physical Cores + 4 HT Cores = 8 Cores)
| Total amount of RAM in Gbytes
||integer|| 80GB (5 * 16GB)
|| Total amount of RAM on each nodes
| average CPU-cores for nodes
||integer|| 8 Cores
|| Number of CPU-cores in average across all nodes
| avarage RAM in Gbytes for nodes
||integer|| 16 GB
|| Amount of memory in average across all nodes
| Operating System on nodes
||String|| Ubuntu 10.04.04 LTS (64bit)
||Linux (specific distribution), Windows (specific distribution), other?|
|Storage system/layer||String|| HDFS
||NFS, HDFS, local files, ?|
| Disk subsystem
||2 x 1TB DISKs; configured as RAID0 => 2TB effective disk space|| Disk subsystem on each node
| HDFS replication factor
|Network layer between nodes||String||The CONTROLLER and the NODEs are connected to a GBit high performance network switch (guarantees the full GBit performance for each port).||Speed of network interfaces, general network speed|
|Controller: CPU specs||String|| 2 x Xeon E5620@2.40GHz Quadcore CPU
|Controller: RAM|| integer
|| 24 GB
|Controller: Disk subsystem||String||3 x 1TB DISKs; configured as RAID5 => 2TB effective disk space||
metrics must come from / be registered in the metrics catalogue
|Metric|| Baseline definition
|| Baseline value
||Goal|| Evaluation 1 (20/8/2012)
|| Evaluation 2 (date)
|| Evaluation 3 (date)
||Serial processing using bash scripts, unix tools and self written java helper tools. Quad core processor 2,66GHz.|| 0,35
|| The baseline workflow incorporates different technologies (script, jar,unix tools) which makes it hard(er) to implement a reliable error handling (compared to a Java map/reduce implementation).
|NumberOfFailedFiles|| Failing on the single input file can be monitored.