ymahlau/fdtdx

Performance measurements

Open

#410 opened on Jul 13, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (66 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (317 stars)
PR merge metrics
 (PR metrics pending)

Description

We should add a single point to store performance measurements of fdtdx on different hardware / different versions / different jax versions. I think a good way is the proposed way in #398, where we have a seperate repository that holds json run files and utilities to display/compare different runtime tests. Possibly it would also be a good idea to move the performance scripts from performance there to have one common place where everything regarding performance measurement lives.

I am happy to hear any suggestions how to realize this best

Contributor guide

Research direction
Explore the proposed approach in issue #398, review the existing performance scripts in the 'performance' directory, and design a structure for a separate repository to store and compare performance measurements. Consider using JSON run files and utilities for display/comparison.
Tech stack
python
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65