Searcharxiv⌕ Search

arXiv subjects

Anika Hennig

Publications and source records attributed to Anika Hennig.

4 recordsLinked to original sources

Perceived Effectiveness of Social Debt Mitigation Measures: A Preliminary Vignette-Based Survey

Software engineering is a socio-technical discipline in which unresolved social and organizational problems accumulate as social debt, gradually eroding collaboration and project health. The literature offers a solid vocabulary for these problems but says little about which countermeasures practitioners consider effective. We address this gap with a vignette-based survey: six social debt problem dimensions (Organizational Silo, Newcomer Isolation, Communication Breakdown, Knowledge Bottleneck, Cultural and Geographical Distance, Psychological Safety Deficit) were presented as realistic team scenarios, and 23 IT professionals and advanced students rated 41 literature-derived mitigation measures. Rankings were analyzed with paired t-tests and a hierarchical Bayesian model that accounts for the within-subject design and yields, for each measure, the probability of being the best option in its scenario. Only for Communication Breakdown is the answer unambiguous: consolidating communication into a single primary channel is almost certainly preferred (P(best)=0.91). For the other five dimensions, the model identifies favorites with moderate evidence (P(best) between 0.38 and 0.58), such as structured knowledge transfer and blameless retrospectives. Across scenarios, structural measures that change how information, decisions, and knowledge are organized were rated higher than role-based or attitudinal measures (by 0.3 to 0.4 scale points), although not in every scenario. Given the small convenience sample, the results are exploratory, but they offer software engineering managers an evidence-graded starting point for selecting mitigation measures.

cs.SE↗

Energy Efficiency of Locally Deployed LLMs: A Preliminary Quantitative GPU Power Benchmark on Consumer Hardware

The local deployment of large language models (LLMs) is gaining traction due to privacy concerns and the desire for on-premise inference. However, the energy costs on consumer hardware remain poorly characterized, as most benchmarks focus solely on accuracy. This paper presents a reproducible, hardware-level energy benchmark of 18 open-source LLMs (0.5B to 7B parameters) executed on a single consumer GPU (RTX 4060ti 16GB). Using the Ollama inference engine, GPU power draw was sampled at 2hz via nvidia-smi across a fixed prompt set. We evaluate mean/peak power, total energy per prompt (J/prompt), energy per output token (J/tok), and throughput (tok/s). Our findings suggest that factors beyond raw parameter count, including model architecture and quantization strategy, drive energy efficiency. Specifically, qwen2.5:0.5b and tinyllama:1.1b achieve the lowest energy cost (0.2747 J/tok and 0.3234 J/tok) and the highest throughput (>325 tok/s). In contrast, the 7B-Mistral model consumes up to 8.6x more energy per token than the most efficient model. Notably, qwen3.5:0.8b(on) exhibits anomalously high per-prompt energy due to extended internal reasoning, highlighting the need to distinguish between token generation modes in efficiency metrics.

cs.AI↗

Measuring and Optimizing Energy Efficiency in ICT: A Multi-vocal Literature Review on Data Centers, Cloud Computing, and LLM-Driven Code Optimization

Rapid growth in Information and Communication Technology (ICT) increases electricity use and environmental impact. Addressing this challenge requires a systematic, software-centric view of how energy and related sustainability attributes are measured, reported, and improved. We present a comprehensive Multi-vocal Literature Review (MLR) integrating peer-reviewed and gray literature to map current practice in measuring and optimizing energy use in ICT software, with emphasis on data centers and cloud computing environments (DCCCEs). First, we synthesize how sustainability is measured across ICT by proposing a taxonomy organized along metric domains (power/energy, energy efficiency, environmental impact) and component granularity (from applications, to containers/VMs, and system-of-systems levels). We summarize measurement approaches and the tooling landscape that implements them. Second, we review optimization strategies at the software and system levels, covering dynamic power and resource management, VM/container consolidation, energy-aware software and system design, and cross-layer, system-wide methods relevant to DCCCEs. Third, we examine how large language models (LLMs) are applied to code generation and transformation for resource-efficient software, noting that most studies target code generation (predominantly in Python) and evaluate runtime and memory, with fewer works directly reporting energy. Hardware- and network-level telemetry are treated as data sources for software-level analysis. We identify gaps in vendor-neutral telemetry, consistent measurement and reporting practices, network-level metrics, and unified, cross-layer optimization frameworks, and outline directions for improving reproducibility and comparability. We screened 635 records (2010-2025) and included 181 sources (122 peer-reviewed, 59 gray).

cs.SE↗

Integrating Energy Efficiency into Software Development: Developer Perspectives and Requirements

In the context of the growing energy footprint of information and communication technology, industry optimization efforts have primarily focused on hardware, while the impact of software on energy consumption is often overlooked. Although technical approaches for optimizing software energy consumption have been developed in research, their adoption in everyday development practice remains limited. This study investigates how software developers perceive energy efficiency in their daily work and which requirements and barriers they formulate for AI-assisted tools supporting energy-aware development. As part of the European GreenCode project, ten semi-structured interviews with professional software developers were conducted and analyzed using qualitative content analysis following Mayrings methodology. The identified requirements were subsequently partly interpreted through the lens of the Technology Acceptance Model. The results indicate that energy efficiency rarely plays an explicit role in daily development activities. Instead, energy savings are typically achieved indirectly through performance optimization. Identified barriers to the explicit consideration of energy efficiency include limited awareness and a strong focus on timely delivery. The interviews further revealed requirements for practical tool support, such as actionable optimization suggestions and seamless integration into common development environments. Furthermore, the acceptance of AI-assisted optimization tools strongly depends on transparency regarding the use of data, the actual energy savings compared to the energy consumption of the tool itself, and the disclosure of the training data used. This study contributes a developer-centered perspective on requirements for energy-aware software development tools and provides insights for designing AI-assisted solutions that align with real-world development practices.

cs.SE↗