Skip to content

Kieker Developers Meeting @ SSP2024

Jump to bottom
DaGeRe edited this page Nov 5, 2024 · 8 revisions

We collect discussion items as the following list for Kieker Developers Meeting at SSP2024. The meeting is scheduled on Tuesday, November 5, 2024 at 14:00.

Discussion List

Kieker Observability Framework tool paper for ICPE 2025

Shinhyung will create a template on Overleaf. This submission targets the Tool Artifact track.

  • Main topic: Observability foundations and whether Kieker fullfils them
  • OceanDSL tools for architecture recovery and identification of interfaces

Stakeholder analysis

Who are our stakeholders? What do they do?

  • Students
    • Getting to know Kieker
    • Using it in lectures (what for?)
  • Researcher
    • Getting to know Kieker
    • Replicating experiments done with Kieker
    • Architecture recovery and analysis (dynamic and static)
    • Performance analysis
    • Instrumenting software
    • Tool development
    • Experimentation
  • Developers
    • Getting to know Kieker
    • Tool development
  • Industry
    • Getting to know Kieker
    • Performance engineering
    • Quality engineering
    • Experimentation
    • Low configuration setup

Kieker refactoring

The size of the Kieker release binary has increased from 650MB to 2.4GB. It requires refactoring.

Every tool comes with its own zip file containing all the necessary dependencies. For the binary bundle, I would suggest to build to merge all the zip files into one.

We can use the approach from OceanDSL:

#!/bin/bash

BASE_DIR=$(cd "$(dirname "$0")"; pwd)

VERSION="1.3.0-SNAPSHOT"

rm -rf $BASE_DIR/build/oceandsl-tools

mkdir -p $BASE_DIR/build/oceandsl-tools
cd $BASE_DIR/build/oceandsl-tools

mkdir bin
mkdir lib

for I in allen-upper-limit cmi dar delta fxca maa mktable mop mvis sar relabel restructuring ; do
	unzip $BASE_DIR/tools/$I/build/distributions/$I-$VERSION.zip
	mv $I-$VERSION/lib/* lib/
	mv $I-$VERSION/bin/* bin/
	rm -rf $I-$VERSION
done

cd ..
tar -cvzpf oceandsl-tools.tgz oceandsl-tools

# end

We should generate the following two bundles:

  • Bundle of all examples (after they have been fixed), source code and setup files only no binaries.
    • All examples must come with a README.md explaining how to use it
    • All examples muss also be part of the documentation on readthedocs
  • Have one tool bundle which contains all tools and its dependencies (see script above)
    • This is for researchers and industry who want to use Kieker
  • Instrumentation is stored on
    • Maven for Java
    • pypi for Python (different repo)
    • Github for C and Fortran (different repo)

Examples

Documentation

We should discuss about the overall structure of the documentation.

Community Outreach

Creating a LinkedIn group such as SIG Software Performance and Monitoring could help increase Kieker's visibility to academia and industry.

More items

Clone this wiki locally