Re: [Pharo-dev] Better Interruption in 2.0
Using Henry's processToInterrupt "Look for best candidate to interrupt: - any scheduled non-finalization process of lower priority - the weak-finalization process, if scheduled - the UI process Never interrupt the idle process, since killing it is fatal" | fallback | fallback := UIManager default uiProcess. Processor scanSchedule: [:p | "suspendedContext sender == nil usually means that process is only scheduled but had no chance to run" ((p ~~ Processor backgroundProcess) and: [ p suspendedContext sender notNil]) ifTrue: [ p ~~ WeakArray runningFinalizationProcess ifTrue: [^p] ifFalse: [fallback := p]] ] startingAt: Processor activePriority. ^fallback in todays Moose 4.8 (on Pharo 20608) on the april 10 VM allows for better interruption, up to the point where the system runs out of memory without a lowspace warning after I assume trying to collect garbage for 20 minutes or so. Stephan
Hi Stephan, I've put a slice to integrate that and the overall UserInterrupt code to get it to work. Can you try it? It's SLICE-Issue-10569-Backport-20-Better-Interrruption-ThierryGoubier.1 in http://ss3.gemtalksystems.com/ss/PharoInbox/ Thierry Le 27/06/2013 00:40, Stephan Eggermont a écrit :
Using Henry's
processToInterrupt "Look for best candidate to interrupt: - any scheduled non-finalization process of lower priority - the weak-finalization process, if scheduled - the UI process Never interrupt the idle process, since killing it is fatal"
| fallback |
fallback := UIManager default uiProcess. Processor scanSchedule: [:p | "suspendedContext sender == nil usually means that process is only scheduled but had no chance to run" ((p ~~ Processor backgroundProcess) and: [ p suspendedContext sender notNil]) ifTrue: [ p ~~ WeakArray runningFinalizationProcess ifTrue: [^p] ifFalse: [fallback := p]] ] startingAt: Processor activePriority. ^fallback
in todays Moose 4.8 (on Pharo 20608) on the april 10 VM allows for better interruption, up to the point where the system runs out of memory without a lowspace warning after I assume trying to collect garbage for 20 minutes or so.
Stephan
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Is this integrated in 2.0 already? Doru On Fri, Jun 28, 2013 at 3:12 PM, Goubier Thierry <thierry.goubier@cea.fr>wrote:
Hi Stephan,
I've put a slice to integrate that and the overall UserInterrupt code to get it to work. Can you try it?
It's SLICE-Issue-10569-Backport-20-**Better-Interrruption-**ThierryGoubier.1 in http://ss3.gemtalksystems.com/**ss/PharoInbox/<http://ss3.gemtalksystems.com/ss/PharoInbox/>
Thierry
Le 27/06/2013 00:40, Stephan Eggermont a écrit :
Using Henry's
processToInterrupt "Look for best candidate to interrupt: - any scheduled non-finalization process of lower priority - the weak-finalization process, if scheduled - the UI process Never interrupt the idle process, since killing it is fatal"
| fallback |
fallback := UIManager default uiProcess. Processor scanSchedule: [:p | "suspendedContext sender == nil usually means that process is only scheduled but had no chance to run" ((p ~~ Processor backgroundProcess) and: [ p suspendedContext sender notNil]) ifTrue: [ p ~~ WeakArray runningFinalizationProcess ifTrue: [^p] ifFalse: [fallback := p]] ] startingAt: Processor activePriority. ^fallback
in todays Moose 4.8 (on Pharo 20608) on the april 10 VM allows for better interruption, up to the point where the system runs out of memory without a lowspace warning after I assume trying to collect garbage for 20 minutes or so.
Stephan
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
-- www.tudorgirba.com "Every thing has its own flow"
On Jun 30, 2013, at 10:15 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Is this integrated in 2.0 already?
No: https://pharo.fogbugz.com/f/cases/10569 Slice needs to be checked.
Doru
On Fri, Jun 28, 2013 at 3:12 PM, Goubier Thierry <thierry.goubier@cea.fr> wrote: Hi Stephan,
I've put a slice to integrate that and the overall UserInterrupt code to get it to work. Can you try it?
It's SLICE-Issue-10569-Backport-20-Better-Interrruption-ThierryGoubier.1 in http://ss3.gemtalksystems.com/ss/PharoInbox/
Thierry
Le 27/06/2013 00:40, Stephan Eggermont a écrit :
Using Henry's
processToInterrupt "Look for best candidate to interrupt: - any scheduled non-finalization process of lower priority - the weak-finalization process, if scheduled - the UI process Never interrupt the idle process, since killing it is fatal"
| fallback |
fallback := UIManager default uiProcess. Processor scanSchedule: [:p | "suspendedContext sender == nil usually means that process is only scheduled but had no chance to run" ((p ~~ Processor backgroundProcess) and: [ p suspendedContext sender notNil]) ifTrue: [ p ~~ WeakArray runningFinalizationProcess ifTrue: [^p] ifFalse: [fallback := p]] ] startingAt: Processor activePriority. ^fallback
in todays Moose 4.8 (on Pharo 20608) on the april 10 VM allows for better interruption, up to the point where the system runs out of memory without a lowspace warning after I assume trying to collect garbage for 20 minutes or so.
Stephan
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
-- www.tudorgirba.com
"Every thing has its own flow"
participants (4)
-
Goubier Thierry -
Marcus Denker -
Stephan Eggermont -
Tudor Girba