trixi-framework/Trixi.jl

Benchmark pre-computing `weights2d`, `weights3d`

Open

#279 opened on Nov 2, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Julia (153 forks)batch import
good first issueperformance

Repository metrics

Stars
 (686 stars)
PR merge metrics
 (Avg merge 9d 1h) (37 merged PRs in 30d)

Description

As suggested by @gregorgassner in https://github.com/trixi-framework/Trixi.jl/pull/274#discussion_r515895414.

Something like weights2d, weights3d could be added to the cache of the semidiscretization.

Contributor guide

Research direction
Start by reviewing the linked PR #274 discussion, especially the comment by @gregorgassner. Examine the current implementation of `weights2d` and `weights3d` in the source code to understand how they are computed. Then, explore the semidiscretization cache structure to identify where to add these precomputed weights. The goal is to benchmark the performance improvement of caching these weights versus computing them on the fly. Consider writing a small script to test both approaches.
Tech stack
None
Domain
performancebackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Julia programmingTrixi.jl cache internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20