August 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Interrupting process which hangs on recursion

by Denis Kudriashov

2016-08-16 9:50 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > I was referring to the fact that when we press Cmd + . , the halt is being > logged in the PharoDebug.log, and this delays the debugger popping up, and > one proposal was to not log these direct user actions. > I would say, this log should include only unhanded exceptions. Anything else like user interrupt or debug action from process browser don't needs to be logged.

Aug. 16, 2016

Re: [Pharo-dev] Interrupting process which hangs on recursion

by Tudor Girba

Hi, I was referring to the fact that when we press Cmd + . , the halt is being logged in the PharoDebug.log, and this delays the debugger popping up, and one proposal was to not log these direct user actions. Cheers, Doru > On Aug 16, 2016, at 9:41 AM, stepharo <stepharo(a)free.fr> wrote: > > What is a user log? > > Stef > > > Le 14/8/16 Ã 09:24, Tudor Girba a Ã©crit : >> Hi, >> >>> On Aug 14, 2016, at 9:14 AM, Max Leske <maxleske(a)gmail.com> wrote: >>> >>> Awesome Denis! >>> >>>> On 13 Aug 2016, at 10:54, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> Very cool analysis! >>>> >>>> What would your proposal be in this case? >>> Some ideas: >>> >>> - perform logging in a separate process >>> - only log user interrupt once for any given time interval, i.e., while a previous interrupt is being logged, ignore logging for further interrupts. >>> >>> Alternatively: donât log user interrupts. I donât really see the value anyway. >> I kind of like the idea of not logging user interrupts. What do others think? >> >> Cheers, >> Doru >> >>> Cheers, >>> Max >>> >>>> Doru >>>> >>>> >>>>> On Aug 13, 2016, at 10:42 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>>>> >>>>> We had discussion on reasons why cmd+. is not always working. >>>>> I made simple test which shows that VM is not issue. Following code normally stops after 20 seconds: >>>>> >>>>> hanging := [1 seconds wait. 1 recursionTest] newProcess. >>>>> hanging priority: Processor activePriority + 10. >>>>> interruptor := [ 20 seconds wait. hanging suspend] newProcess. >>>>> interruptor priority: Processor activePriority + 11. >>>>> >>>>> hanging resume. >>>>> interruptor resume. >>>>> >>>>> Recursion method: >>>>> Integer>>recursionTest >>>>> self recursionTest >>>>> >>>>> Hanging process produces 7 million contexts on my machine: >>>>> >>>>> c := hanging suspendedContext. >>>>> count := 1. >>>>> [ c notNil ] whileTrue: [ c := c sender. count := count + 1 ]. >>>>> count Â«7395279" >>>>> >>>>> But if you try to debug it by "hanging debug" you will see how it is slow. It's caused by printing stack to file. >>>>> Interesting that logging is performed before opening debugger. So every time we press cmd+. we are waiting logging to see debugger. >>>>> >>>>> We need to change this logic. >>>>> >>>>> Best regards, >>>>> Denis >>>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "One cannot do more than one can do." >>>> >>>> >>>> >>>> >>>> >>> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Yesterday is a fact. >> Tomorrow is a possibility. >> Today is a challenge." >> >> >> >> >> >> > > -- www.tudorgirba.com www.feenk.com "Being happy is a matter of choice."

Aug. 16, 2016

Re: [Pharo-dev] [ANN] Release of Agile Visualization

by stepharo

Le 14/8/16 Ã 23:19, Alexandre Bergel a Ã©crit : > Dear Colleagues and Friends, > > It is a great pleasure to announce the release of Agile Visualization. Agile Visualization is a book about the Roassal Visualization engine. > > Paperback, eBook (PDF), and a free HTML format chapters are available from http://AgileVisualization.com > The book has 235 pages and covers the essential aspects of Roassal. Copies of the book will be sold at ESUGâ16. keep on for me :) > > Screenshots and codes contained in the book were produced on Pharo. However, most of the covered code and topics _equally_run on VisualWorks (from version 7.4 (!)). > > We would like to thank all the contributors and users of Roassal who have deeply impacted and shaped Agile Visualization. The book is dedicated to the Smalltalk community at large. Big big thanks to our sponsors, Lam Research, Object Profile, and ESUG. > And thanks to you for being as you are and making Smalltalk such a great platform. > > Thanks > Alexandre > > >

Aug. 16, 2016

Re: [Pharo-dev] Interrupting process which hangs on recursion

by stepharo

What is a user log? Stef Le 14/8/16 Ã 09:24, Tudor Girba a Ã©crit : > Hi, > >> On Aug 14, 2016, at 9:14 AM, Max Leske <maxleske(a)gmail.com> wrote: >> >> Awesome Denis! >> >>> On 13 Aug 2016, at 10:54, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Very cool analysis! >>> >>> What would your proposal be in this case? >> Some ideas: >> >> - perform logging in a separate process >> - only log user interrupt once for any given time interval, i.e., while a previous interrupt is being logged, ignore logging for further interrupts. >> >> Alternatively: donât log user interrupts. I donât really see the value anyway. > I kind of like the idea of not logging user interrupts. What do others think? > > Cheers, > Doru > >> Cheers, >> Max >> >>> Doru >>> >>> >>>> On Aug 13, 2016, at 10:42 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>>> >>>> We had discussion on reasons why cmd+. is not always working. >>>> I made simple test which shows that VM is not issue. Following code normally stops after 20 seconds: >>>> >>>> hanging := [1 seconds wait. 1 recursionTest] newProcess. >>>> hanging priority: Processor activePriority + 10. >>>> interruptor := [ 20 seconds wait. hanging suspend] newProcess. >>>> interruptor priority: Processor activePriority + 11. >>>> >>>> hanging resume. >>>> interruptor resume. >>>> >>>> Recursion method: >>>> Integer>>recursionTest >>>> self recursionTest >>>> >>>> Hanging process produces 7 million contexts on my machine: >>>> >>>> c := hanging suspendedContext. >>>> count := 1. >>>> [ c notNil ] whileTrue: [ c := c sender. count := count + 1 ]. >>>> count Â«7395279" >>>> >>>> But if you try to debug it by "hanging debug" you will see how it is slow. It's caused by printing stack to file. >>>> Interesting that logging is performed before opening debugger. So every time we press cmd+. we are waiting logging to see debugger. >>>> >>>> We need to change this logic. >>>> >>>> Best regards, >>>> Denis >>>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "One cannot do more than one can do." >>> >>> >>> >>> >>> >> > -- > www.tudorgirba.com > www.feenk.com > > "Yesterday is a fact. > Tomorrow is a possibility. > Today is a challenge." > > > > > >

Aug. 16, 2016

Re: [Pharo-dev] Interrupting process which hangs on recursion

by stepharo

Thanks denis. So our discussions were good :) Le 13/8/16 Ã 10:42, Denis Kudriashov a Ã©crit : > We had discussion on reasons why cmd+. is not always working. > I made simple test which shows that VM is not issue. Following code > normally stops after 20 seconds: > hanging := [1 seconds wait. 1 recursionTest] newProcess. > hanging priority: Processor activePriority + 10. > interruptor := [ 20 seconds wait. hanging suspend] newProcess. > interruptor priority: Processor activePriority + 11. > > hanging resume. > interruptor resume. > > Recursion method: > Integer>>recursionTest > self recursionTest > > Hanging process produces 7 million contexts on my machine: > > c := hanging suspendedContext. > count := 1. > [ c notNil ] whileTrue: [ c := c sender. count := count + 1 ]. > count Â«7395279" > > > But if you try to debug it by "hanging debug" you will see how it is > slow. It's caused by printing stack to file. > Interesting that logging is performed before opening debugger. So > every time we press cmd+. we are waiting logging to see debugger. > > We need to change this logic. > > Best regards, > Denis >

Aug. 16, 2016

Re: [Pharo-dev] [ANN] Release of Agile Visualization

by Markus Fritsche

Hello Alexandre, congratulations on finishing your book! Am 14.08.2016 23:19, schrieb Alexandre Bergel: > Paperback, eBook (PDF), and a free HTML format chapters are available > from http://AgileVisualization.com Do you have an intermediary format that could be Output to epub (preferred) or mobi? I'd like to buy the eBook, but tbh, pdf reflow isn't that great on readers, so I don't like to buy "the cat in the bag" (german idiom). Best regards, Markus

Aug. 16, 2016

Re: [Pharo-dev] [Moose-dev] [ANN] Release of Agile Visualization

by Serge Stinckwich

Congrats Alex for this nice book. Thank you for pushing us to participate to one chapter. On Sun, Aug 14, 2016 at 11:19 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Dear Colleagues and Friends, > > It is a great pleasure to announce the release of Agile Visualization. Agile Visualization is a book about the Roassal Visualization engine. > > Paperback, eBook (PDF), and a free HTML format chapters are available from http://AgileVisualization.com > The book has 235 pages and covers the essential aspects of Roassal. Copies of the book will be sold at ESUGâ16. > > Screenshots and codes contained in the book were produced on Pharo. However, most of the covered code and topics _equally_run on VisualWorks (from version 7.4 (!)). > > We would like to thank all the contributors and users of Roassal who have deeply impacted and shaped Agile Visualization. The book is dedicated to the Smalltalk community at large. Big big thanks to our sponsors, Lam Research, Object Profile, and ESUG. > And thanks to you for being as you are and making Smalltalk such a great platform. > > Thanks > Alexandre > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Aug. 16, 2016

Re: [Pharo-dev] [Moose-dev] [ANN] Release of Agile Visualization

by HernÃ¡n Morales Durand

Congratulations Alex. Thank you for all the great work! HernÃ¡n 2016-08-14 18:19 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Dear Colleagues and Friends, > > It is a great pleasure to announce the release of Agile Visualization. > Agile Visualization is a book about the Roassal Visualization engine. > > Paperback, eBook (PDF), and a free HTML format chapters are available from > http://AgileVisualization.com > The book has 235 pages and covers the essential aspects of Roassal. Copies > of the book will be sold at ESUGâ16. > > Screenshots and codes contained in the book were produced on Pharo. > However, most of the covered code and topics _equally_run on VisualWorks > (from version 7.4 (!)). > > We would like to thank all the contributors and users of Roassal who have > deeply impacted and shaped Agile Visualization. The book is dedicated to > the Smalltalk community at large. Big big thanks to our sponsors, Lam > Research, Object Profile, and ESUG. > And thanks to you for being as you are and making Smalltalk such a great > platform. > > Thanks > Alexandre > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev >

Aug. 16, 2016

Re: [Pharo-dev] [Moose-dev] [ANN] Release of Agile Visualization

by Chris Muller

Finishing a book is hard. Your work and perseverence has elevated this project to an amazing level. Congratulations, Alexandre. On Sun, Aug 14, 2016 at 4:19 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Dear Colleagues and Friends, > > It is a great pleasure to announce the release of Agile Visualization. Agile Visualization is a book about the Roassal Visualization engine. > > Paperback, eBook (PDF), and a free HTML format chapters are available from http://AgileVisualization.com > The book has 235 pages and covers the essential aspects of Roassal. Copies of the book will be sold at ESUGâ16. > > Screenshots and codes contained in the book were produced on Pharo. However, most of the covered code and topics _equally_run on VisualWorks (from version 7.4 (!)). > > We would like to thank all the contributors and users of Roassal who have deeply impacted and shaped Agile Visualization. The book is dedicated to the Smalltalk community at large. Big big thanks to our sponsors, Lam Research, Object Profile, and ESUG. > And thanks to you for being as you are and making Smalltalk such a great platform. > > Thanks > Alexandre > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

Aug. 15, 2016

Re: [Pharo-dev] Performance of [ * ] repeat vs [ * . true ] whileTrue

by Eliot Miranda

On Mon, Aug 15, 2016 at 9:11 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > > On Mon, Aug 15, 2016 at 12:54 AM, John Brant <brant(a)refactoryworkers.com> > wrote: > >> >> > On Aug 14, 2016, at 4:42 PM, Henrik Nergaard <henrik.nergaard(a)uia.no> >> wrote: >> > >> > Hi, >> > >> > Why is â[ * ] repeatâ almost twice as slow as â[ * . true ] whileTrueâ >> ? >> >> #repeat isnât optimized by the compiler like #whileTrue is. I donât know >> if there is a reason for this, but most every other Smalltalk (Squeak, VW, >> & Dolphin) optimize the #repeat method. >> >> >> On Squeak it's optimized by default too. > > I had an intern adding that as a bytecode compiler option and make the > decompiler compliant with this. One needs to check if everything still > works fine but it can be enabled. Something like: <compilerOptions: + > inlineRepeat> should already work. > > I think the idea was to keep limited the number of inlined messages, hence > that one is not inlined by default. #timesRepeat: is not inlined either in > Pharo. But then where's the limit between what you inline and what you > don't... > And arguably when we have Sista/Scorch we can reduce the number of optimized selectors, but only if we don't care about pure interpreter performance. > John Brant >> > _,,,^..^,,,_ best, Eliot

Aug. 15, 2016