#12498 closed enhancement (fixed)
Slow boot with many "administrative" entries
Reported by: | humdinger | Owned by: | leavengood |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | System/Boot Loader | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #12525, #13318 | |
Platform: | All |
Description
This is hrev49872.
I noticed a long delay (> 2 sec.) before the boot logo appears. It turned out, that I had over 200 subfolders in /system/packages/administrative/. After removing everything but the newest 20 of them, that delay disappeared.
Of course I don't need 200+ fallback states and I don't have a problem deleting those from time to time (until some prefs panel will allow me to set up an "auto-clean" maybe in the future).
I was wondering though, why it's even an issue to have many fallback-states when booting. Surely this list of fallbacks is only of interest when entering the boot options and not for a regular boot?
Change History (8)
comment:1 by , 9 years ago
Blocking: | 12525 added |
---|
comment:2 by , 9 years ago
here a solution to solve this: http://besly.de/menu/search/archiv/pref/avoid-longer-boot-times.html
comment:3 by , 9 years ago
I would also assume that the old states should not need to be checked upon when launching the current state. However, it's probably just the default behavior, and it would resolve older packages from there if they are missing in the current state.
The problem with 20 states is that you don't know if that suffices, or not; only the changed packages are stored, so it may happen that you need a much older one when switching to a recent state. AFAICT, a better solution than to delete old states would be to merge them, ie. move all newer states to be removed to the last state available (replacing any package with the same base name), and then rename that last state to the most recent removed state.
follow-up: 5 comment:4 by , 8 years ago
Blocking: | 13318 added |
---|
comment:5 by , 7 years ago
Replying to axeld:
It is important here to find a solution for the later beta version, otherwise come various bug messages because of a haiku system which boots slower and slower.
Here is a current discussion about it: https://discuss.haiku-os.org/t/slow-boot-times-after-months-of-using-haiku
comment:6 by , 5 years ago
Owner: | changed from | to
---|---|
Status: | new → in-progress |
I have a work in progress patch to fix the boot speed issue: https://review.haiku-os.org/c/haiku/+/1703
Later I will see about making the package_server clean up old package states.
comment:8 by , 5 years ago
Milestone: | Unscheduled → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
(In #12525) It's probably the same issue I reported as #12498.