Record a reproducible large-map performance baseline on Windows
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- cpp
- Domain
- performance
Research direction
Start with the profiling guide at docs/map-loading-performance.md and the existing profiling script it describes. Run five fresh-process openings and five reopenings using identical map and client settings, then report median first-frame time, peak RAM, and the listed build and machine details. Done means a comparable measurement summary is posted without private files or machine-specific paths.
Written by the indexing model from the issue text.
Description
DME already records the time to the first complete frame and peak memory with --load-profile. Use the profiling guide and the existing script to collect comparable results on recent builds.
- Run five fresh-process openings and five reopenings in one process with the same map, client, renderer, zoom and settings.
- Report median time to the first complete frame and peak RAM, plus the DME build, Windows version, CPU, GPU, graphics backend, client profile and approximate map size.
- If editing feels slow after load, report the exact pan, zoom, selection or save steps separately.
A summary of the measurements is enough. Keep private maps, client files and machine-specific paths out of public reports.
- Dominant language
- C++
- Stars
- 12
- Forks
- 10
- Avg merge
- 4h 38m
- Merged PRs (30d)
- 38
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dewral/DewralMapEditor
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dewral/DewralMapEditor#88 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
dewral/DewralMapEditor#91 ·
Maintainers usually reply within 1 day
All issues in dewral/DewralMapEditor
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Malformed mark-up in translationsPossibly taken A pull request linked to this issue is open or already merged. OpenBug Translations
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
wesnoth/wesnoth#11728 · 1 comment ·
Maintainers usually reply within 1 day
-
Articulation cache docs swap the eFIX_BASE condition for the root DoF termsPossibly taken @NeoZng claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
NVIDIA-Omniverse/PhysX#600 ·
Maintainers usually reply within 1 day