Very slow performance opening layouts/workspaces
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- cli, performance
Research direction
Reproduce the delay with the provided layout.yaml example, repeating its two-window pattern to reach 12 windows and 18 panes. Trace the workspace-opening entry point and measure where startup time is spent; done means the example opens substantially faster without changing its resulting layout, with a regression check for the reported case.
Written by the indexing model from the issue text.
Description
I used to use this project a while ago, recently I wanted to incorporate it again in a few of my scripts but it seems like opening layouts takes a significant amount of time.
Simple layouts (2 windows where 1 window is a split pane with simple commands prefilled) can take several seconds to open. It seems to linearly scale with the amount of windows as well.
This feels like something that should take milliseconds, not seconds.
Here is an extreme example of a workspace that took 25 seconds!
✓ Loaded workspace: work/haystack (~/.config/tmux-layouts/projects/work/haystack/layout.yaml) [12 win, 18 panes]
Session created in detached state.
[detached (from session work/haystack)]
~ took 25s
Repeat the following windows 6 times (for 12 total windows) and you've got the layout from above:
session_name: ${SESSION_NAME}
start_directory: ${PROJECT_DIR}
windows:
- window_name: Editor
layout: main-vertical
focus: true
options:
main-pane-width: 75%
panes:
- shell_command: nvim
focus: true
- null
- panes:
- null
It's especially jarring because I feel like it definitely did not take this long with a version from months ago, though I can't say that with certainty.
This project so far does provide the most flexibility and features that I'd like to have, so thanks for the effort! <3
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 248
- Avg merge
- 2h 13m
- Merged PRs (30d)
- 1
Contributor guide
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 tmux-python/tmuxp
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
tmux-python/tmuxp#1026 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
tmux-python/tmuxp#939 · 1 comment ·
-
enhancement WorkspaceBuilder
Difficulty 4/5 3-5 days Newbie friendliness 48/100
tmux-python/tmuxp#1062 ·
-
enhancement need-comments WorkspaceBuilder
Difficulty 5/5 Over a week Newbie friendliness 35/100
tmux-python/tmuxp#1058 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
tmux-python/tmuxp#1051 ·
All issues in tmux-python/tmuxp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100