Home

Welcome to the everBeen wiki!

About BEEN

BEEN is a universal benchmarking platform written in Java. It was originally tailored to benchmarking middleware, but progressively grew more ambitious and became more universal. Nowadays, it's undergoing some pretty rough measures that should make it simpler and easier to deploy.

Developer team

As of now, the developer team consists of the following members (alphabetically):

• Andrej Podzimek, a.k.a. AP - the team's mentor.
• Martin Sixta, a.k.a. MS, a.k.a. sixtam - team leader.
• Radek Macha, a.k.a. RM, a.k.a. darklight - developer.
• Tadeas Palusga, a.k.a. TP, a.k.a. donarus - developer.
• Jakub Brecka, a.k.a. JB, a.k.a. cube - developer.

Developer meetings

The developer team is organizing regular meetings. These meetings are documented and you can read the protocols using the link below. Meeting Protocols

Code conventions

Some coding conventions

• Commit convention
• Slf4j over logback
• Build how to
• Class layout
• Eclipse formatter

TODO checklist before turn-in

• Persistence querying
• Load monitor samples persistence
• Service logging hooks for BEEN services
• Configuration persistence
• Entity deletion (TaskContext, Benchmark, with restrictions on what can be deleted)
• Result eviction on Task or TaskContext fail
• Benchmark API
• Result visualisation on the Web Interface
• BEEN configuration tune-up and documentation
• [-] Limitation of data rendered with live-action graphs on the Web Interface
• [-] Windows testing
• Web interface embedded deployment
• Web interface style unification
• Web interface log view stack-trace expansion
• Task planner
• Hazelcast benchmark
• Task (with leftover data deletion)/TaskContext/Benchmark detail
• Web Interface benchmark run workflow
• Web Interface exception handling if some BEEN services are not running (Been API exceptions)
• [-] Web page displaying services (status + logs)
• Host detail page (+ cache and leftover task data delete)
• In-code TODO/FIXME scan

Documentation

We've assembled a Documentation TOC to organize our efforts of providing BEEN users with a sensible but sufficient amount of information.

Requirements

• An active MongoDB database on the node which provides persistence layer (Repository is running). There is a bug in MongoDB 1.4.4 (current Debian stable version) which prevents Mongo object ID (_id) to be left out of the queried objects, which causes problems when deserializing queried persistent objects. Using a reasonably up-to-date version is highly recommended.

Commitee presentation checklist

• Sample deployment (either of VM farms)
• Finished benchmarks with some results to show

Feature wish-list

Here are some ideas for features we would like to implement in the future.