Replies: 2 comments 5 replies
-
It might be interesting to think about pooling the instances, but I'm not sure if that is the correct way to solve the present problem because the 5-second delay seems unusual in my experience. For example, the startup is about 0.2 seconds with my settings of
$ PS1='\$ ' bash --norc # start a child Bash session with a plain setting
$ echo $EPOCHREALTIME; source /path/to/ble.sh --norc --attach=attach; echo $EPOCHREALTIME
$ exit
$ PS1='\$ ' bash --norc # start another Bash session with a plain setting
$ echo $EPOCHREALTIME; source /path/to/ble.sh --attach=attach; echo $EPOCHREALTIME
$ exitIf the delay is not caused by the loading of
If it is the status bar set up by
In the exit phase,
I don't think the exit delay is caused by the
With |
Beta Was this translation helpful? Give feedback.
-
|
@bkerin By the way, in GitHub Discussion, could you reply to the comment thread rather than making a separate thread every time you reply? edit: I think the GitHub interface is strange, but you need to reply on the web page rather than replying via email. |
Beta Was this translation helpful? Give feedback.
-
$ echo $EPOCHREALTIME; source ~/.local/share/blesh/ble.sh --norc --attach=attach; echo $EPOCHREALTIME $ echo $EPOCHREALTIME; source ~/.local/share/blesh/ble.sh --attach=attach; echo $EPOCHREALTIME So it's something in my .bashrc. It's fast by itself but apparently induces ble.sh to do something slow. Exit is also very fast with
It's the status bar of ble.sh that gets the extra draw. In the screenshot it's the gray bar with ~. It's set with
It takes about a second in my slow setup. I'll determine what in my existing .bashrc is causing this also. |
Beta Was this translation helpful? Give feedback.
-
|
Well with pretty much everything removed I started looking for other causes and it looks like this non-branded external battery I just got is getting sensed (or not sensed) and causing some major CPU throttling. Congrats to ble.sh for being the first thing to work computer hard enough to show the problem :) |
Beta Was this translation helpful? Give feedback.
-
Thank you for the information. If the delay is caused in ble.sh by some interference with the other configurations, I'll take a look if there is sufficient information to reproduce the problem.
If something is making ble.sh slow, one possibility would be through
Yeah, admittedly, ble.sh consumes much more computational resources compared to plain Bash. I think the CPU usage wouldn't be a real issue, but the large memory footprint is one of the recent problems of |
Beta Was this translation helpful? Give feedback.
-
|
Since maybe other users will find ble.sh reveals a throttling problem here is a pointer to what worked for me. It's probably most likely to solve the issue for Dell laptops but maybe others do the same tricks. The answer is here except you should and with 0xFFFFFFFE (issue reported already): https://github.com/yyearth/turnoff-BD-PROCHOT so to see the value to set: or to script it: Top guy here is right, it's just a scam from dell to get money from you I've had exactly the issue he describes with a power supply previously and this is just the same garbage for non-dell external batteries (the one I have has greater current capacity the dell external batteries and still it use PROCHOT to hurt them): |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, that's an interesting story. Thank you for sharing the tip. |
Beta Was this translation helpful? Give feedback.
-
I'm really liking ble.sh so far but there is one issue that's still interfering with regular use for me and that's the startup time. It's only about 5 seconds but I use dwm and have habit of often creating new windows with a terminal when investigating side issues and the like, at 5 seconds it becomes annoying.
I thought of using tmux to just start a pool of instances and then attach to them from a bare-bones shell, it seems to work pretty well like so:
I think a pool server should be a quick hack (tm) to do but thought I would ask if something like it has already been done or there is some better way already?
Also there is one small visual artifact that suggest some sort of race or something is going on (see attached screenshot). A copy of the status bar appears in the middle of the terminal for some reason.
Even a tiny delay hides this issue:
xfce4-terminal --execute bash -c "sleep 0.05; ~/local/bin/tmux attach-session -t shell_pool_1"Also the terminal is a tiny bit slower to vanish again than I would like, I think because the [ble: exit] indicator. I would swear I saw a way to remove that, but the only two options I found going back through is exec_errexit_mark= which only affects behavior of commands, not the mark for exit of ble.sh itself. builtin exit isn't quite enough either as there is some trap running. kill -9 $$ works but seems cruel :). I didn't find out what in the ble.sh exit is pausing things.
Beta Was this translation helpful? Give feedback.
All reactions