[squeak-dev] [Vm-dev] The Trunk: System-codefrau.1205.mcz
David T. Lewis
lewis at mail.msen.com
Tue Jan 5 16:28:54 UTC 2021
On Tue, Jan 05, 2021 at 09:58:22AM +0100, Marcel Taeumel wrote:
> Hi all!
> At the time of writing, the wizard has a hard-coded list of somewhat costly preferences to turn off via #adjustSettingsForLowPerformance. We should check and update that list from time to time.
> The check for #isLowerPerformance may also be useful outside the scope of preferences. Well, maybe we can make it check the *remaining* resources for new workload to come. That is, there may already be a Squeak process eating up 99% of the image's resources. Then, any call to #isLowerPerformance should answer "true", of course. Even though we might be on a powerful machine. The current workload matters for the upcoming operations.
> Note that the current workload is expected to be low at image-startup time. ;-) So, somehow deriving a performance figure at that time makes sense to me.
> Here is a summary of your suggestions:
> A) Estimate processor mips from platform specs
> + eem
> o mt
> B) Take extra measurement via #timeToRun when checking #isLowerPerformance, may be cached
> + dtl
> + tpr
> o codefrau
> - eem??
> - mt
> C) Profile image start-up via VM parameter 20 or similarly cheap timestamps
> + ul
> + codefrau
> + eem
> + dtl
> + mt
> All in all, we should follow up on Levente's suggestion.
+1 for using Levente's approach
More information about the Squeak-dev