You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The whole thing is composed by a number of pieces each of which may have different needs at initialisation time.
For instance, Launchpad may (or may not) need to scan ResourceFS (this depends if the user has decided to use RISC OS old ResourceFS based Apps approach or not). LaunchPad will always need to read its ObjectDB file (if present) and for each entry in the ObjDB, it will need to read the !Boot info and verify that that entry still exists.
So, I am trying to implement a fully multi-tasking initialisation of each component that may result in something like:
gantt
section DME Components Boot
axisFormat taskTime
Total boot :done, des1, 0s,6s
DeskRes :active, des2, 0s, 2s
DeskCfg : des3, after des2, 1s
PowerFiler : des4, after des3, 1s
LaunchPad : des5, after des3, 3s
Notifications: des6, after des4, 2s
Loading
Obviously RISC OS may not have a performance boost from this, but it may help to get to a usable Desktop in less time than by using single task initialisation for each component.
Timing is indicative only right now, 'cause it will depends on each component when completed, the amount of data required to initialise, the platform and the FileSystem performance for each different media type.
documentationImprovements or additions to documentationdiscussionwe need to discuss this and come up with a plan
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The whole thing is composed by a number of pieces each of which may have different needs at initialisation time.
For instance, Launchpad may (or may not) need to scan ResourceFS (this depends if the user has decided to use RISC OS old ResourceFS based Apps approach or not). LaunchPad will always need to read its ObjectDB file (if present) and for each entry in the ObjDB, it will need to read the !Boot info and verify that that entry still exists.
So, I am trying to implement a fully multi-tasking initialisation of each component that may result in something like:
Obviously RISC OS may not have a performance boost from this, but it may help to get to a usable Desktop in less time than by using single task initialisation for each component.
Timing is indicative only right now, 'cause it will depends on each component when completed, the amount of data required to initialise, the platform and the FileSystem performance for each different media type.
Beta Was this translation helpful? Give feedback.
All reactions