On 09-02-2015, at 1:00 PM, Norbert Hartl <email@example.com> wrote:
We’d need some input from someone that really knows Morphic. You could try running in an MVC project and see if it makes any difference?
Am 09.02.2015 um 21:39 schrieb tim Rowledge <firstname.lastname@example.org>:Thanks for the analysis. Not being an expert on _all_ those topics :) I'm asking myself if there are some tweaks (monkey patching is fine) to get rid of those? I certainly do not need any morphic loop as long as it doesn't steer the network reception *cough* :)
On 09-02-2015, at 12:33 PM, email@example.com wrote:
Can't the box be setup 5o do some WoL thing and go back to sleep when idling for a while?
This CPU usage is really annoying indeed.
Assuming you are using a stack or Cog vm, that will mostly be the heartbeat that checks for inputs and process switches and GC limits etc. Plus any remaining morphic loop etc.
Pharo does not have MVC anymore.
Can the intervals to check inputs and process switches be stretched without open the door to hell because timing loops are tightly aligned?Maybe. Eliot?tim--tim Rowledge; firstname.lastname@example.org; http://www.rowledge.org/timWhat passes for common sense is always revisable