- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [IMPORTANT] Starting migration to Spur VM

by Torsten Bergmann

Exciting times indeed! Many thanks to all who work on this/prepare this. But we should also be aware: 1. many people already use Pharo 5 as it is very usable and stable I think this deserves a better naming/closing before the integration than just a simple update number. Would it make sense to close down the Pharo 5 line and start with the Spur thing as Pharo 6 as this would make it more easily distinguishable? Especially since Pharo 5 is very stable, already really usuable and with Spur we do not follow our mantra of small steps. This would really avoid confusion afterwards within and outside of the community. 2. the VM change might affect PharoLauncher images as well. It would be good to still have a PharoLauncher that can launch old non-spur (up to now) and new spur-based images Thanks T.

Dec. 14, 2015

Re: [Pharo-dev] [Pharo-users] New web tutorial

by Norbert Hartl

Looks good but I don't understand it :) Norbert > Am 13.12.2015 um 22:13 schrieb stepharo <stepharo(a)free.fr>: > > Hi guys > > with Olivier Auverlot we did several attempts (over the year) and we are happy to release a first draft of a web tutorial > around Pharo. We ask the user to build a simple blog engine. > > It goes over > - Mongo > - Seaside > - Magritte > > https://ci.inria.fr/pharo-contribution/job/TinyBlogTutorial/5/artifact/book… > > Soon Rest/Deployment/Garage?/NeoJSON/XML > > If you want to participate (translate it to english) or improve it you are welcome. > > We hope that it will serve as a basis to a lot of Seaside applications. > > This tutorial will be used in the lecture I'm giving next weeks in Togo and will be edited as a lulu book. > > Stef and Olivier. > > > >

Dec. 14, 2015

Re: [Pharo-dev] [IMPORTANT] Starting migration to Spur VM

by Esteban A. Maringolo

2015-12-14 10:14 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: > Thank you Eliot & Esteban for making this happen! +1 I look forward to see this in action! :)

Dec. 14, 2015

Re: [Pharo-dev] [IMPORTANT] Starting migration to Spur VM

by Tudor Girba

Thank you Eliot & Esteban for making this happen! Exciting times :) Cheers, Doru > On Dec 14, 2015, at 11:24 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > We will start migration to Spur today. > To complete it, we will require some time, specially to adapt the CI and check everything is ok. > > Spur will allow us to do a big step forward in Pharo development, in the concrete you will see it immediately for this: > - We have noticed a speed increment of 100% in tiny benchmarks (and according to Eliot, it will be at least 35% in general on the system). > - No more GC stops (noticeable when running large systems) > - We will be able to scale our systems up to 2G memory consumption without loosing performance. > > But, this will have some drawbacks in the first times: > > 1) VM will not be compatible between versions anymore: Pharo 5.0 will have a Pharo Spur VM associated (and they are not compatible). > - There WILL NOT be a "non-spur" version of Pharo 5.0. Once completed the transitions, this will be the only one. > > 2) NativeBoost-FFI implementation has been replaced with a new implementation who relies in ThreadedFFIPlugin and IA32Plugin. While we worked a lot to do this transition as painless as possible and we achieve a good level of backward compatibility (most uses of #nbCall: should work out of the box), there are some problems we cannot solve: > - there are some stuff not possible to compatibilise, notably: > - Structures now need to inherit from FFIExternalStructure > - Arrays now are now shadowed > - in general is a bit slower (impossible to compete with ASM) but in general is not perceptible. > - THERE WILL BE BUGS AND NON-IMPLEMENTED FEATURES: Current implementation is validated with Athens and even Roassal was working, but of course that does not covers all cases. > 2.1) ASMJIT will be removed from system and put in a separated packages. > NOTE: There will be a blog post explaining FFI-NB architecture during the week. > > 3) There are more or less 70 new failing tests, some of them important than we need to fix as soon as possible. Please, please, please, help us with them :) > > 4) In general we foresee the system will became unstable some weeks, before it gets back to normal. Please be patient. > > 5) You will need to adapt your Pharo 5.0 related apps and CI processes (to take care about new VM). Some programs will stop work at all (for example, I think Pharo-launcher will need to be adapted). > > -- www.tudorgirba.com www.feenk.com "Presenting is storytelling."

Dec. 14, 2015

Re: [Pharo-dev] [Pharo-users] [IMPORTANT] Starting migration to Spur VM

by Esteban Lorenzano

> On 14 Dec 2015, at 12:07, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > 30% - 100% wow thats quite a speed boost, well done guys! > And 2GB images are more than welcomed , especially for me that I have to deal with 3d data. > > Does that ThreadedFFIPlugin means we can now use C libraries that use threading ? not yetâ¦ but that is the path :) > > On Mon, Dec 14, 2015 at 1:01 PM Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: > Thanks! > > > On 14 dic 2015, at 11:32 a.m., Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > > > > > >> On 14 Dec 2015, at 11:24, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > >> > >> We will start migration to Spur today. > >> To complete it, we will require some time, specially to adapt the CI and check everything is ok. > >> > >> Spur will allow us to do a big step forward in Pharo development, in the concrete you will see it immediately for this: > >> - We have noticed a speed increment of 100% in tiny benchmarks (and according to Eliot, it will be at least 35% in general on the system). > >> - No more GC stops (noticeable when running large systems) > >> - We will be able to scale our systems up to 2G memory consumption without loosing performance. > >> > >> But, this will have some drawbacks in the first times: > >> > >> 1) VM will not be compatible between versions anymore: Pharo 5.0 will have a Pharo Spur VM associated (and they are not compatible). > >> - There WILL NOT be a "non-spur" version of Pharo 5.0. Once completed the transitions, this will be the only one. > >> > >> 2) NativeBoost-FFI implementation has been replaced with a new implementation who relies in ThreadedFFIPlugin and IA32Plugin. While we worked a lot to do this transition as painless as possible and we achieve a good level of backward compatibility (most uses of #nbCall: should work out of the box), there are some problems we cannot solve: > >> - there are some stuff not possible to compatibilise, notably: > >> - Structures now need to inherit from FFIExternalStructure > >> - Arrays now are now shadowed > >> - in general is a bit slower (impossible to compete with ASM) but in general is not perceptible. > >> - THERE WILL BE BUGS AND NON-IMPLEMENTED FEATURES: Current implementation is validated with Athens and even Roassal was working, but of course that does not covers all cases. > >> 2.1) ASMJIT will be removed from system and put in a separated packages. > >> NOTE: There will be a blog post explaining FFI-NB architecture during the week. > >> > >> 3) There are more or less 70 new failing tests, some of them important than we need to fix as soon as possible. Please, please, please, help us with them :) > >> > >> 4) In general we foresee the system will became unstable some weeks, before it gets back to normal. Please be patient. > >> > >> 5) You will need to adapt your Pharo 5.0 related apps and CI processes (to take care about new VM). Some programs will stop work at all (for example, I think Pharo-launcher will need to be adapted). > >> > > > > ah, I forget it! > > > > 6) Some changes to the VM accumulated during the time of transition (some months now). So, some changes introduced there will not be present in new VM. I will merge this changes in the next weeks. > > > > cheers! > > Esteban > >

Dec. 14, 2015

Re: [Pharo-dev] [IMPORTANT] Starting migration to Spur VM

by Dimitris Chloupis

30% - 100% wow thats quite a speed boost, well done guys! And 2GB images are more than welcomed , especially for me that I have to deal with 3d data. Does that ThreadedFFIPlugin means we can now use C libraries that use threading ? On Mon, Dec 14, 2015 at 1:01 PM Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Thanks! > > > On 14 dic 2015, at 11:32 a.m., Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > > > > >> On 14 Dec 2015, at 11:24, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> > >> We will start migration to Spur today. > >> To complete it, we will require some time, specially to adapt the CI > and check everything is ok. > >> > >> Spur will allow us to do a big step forward in Pharo development, in > the concrete you will see it immediately for this: > >> - We have noticed a speed increment of 100% in tiny benchmarks (and > according to Eliot, it will be at least 35% in general on the system). > >> - No more GC stops (noticeable when running large systems) > >> - We will be able to scale our systems up to 2G memory consumption > without loosing performance. > >> > >> But, this will have some drawbacks in the first times: > >> > >> 1) VM will not be compatible between versions anymore: Pharo 5.0 will > have a Pharo Spur VM associated (and they are not compatible). > >> - There WILL NOT be a "non-spur" version of Pharo 5.0. Once > completed the transitions, this will be the only one. > >> > >> 2) NativeBoost-FFI implementation has been replaced with a new > implementation who relies in ThreadedFFIPlugin and IA32Plugin. While we > worked a lot to do this transition as painless as possible and we achieve a > good level of backward compatibility (most uses of #nbCall: should work out > of the box), there are some problems we cannot solve: > >> - there are some stuff not possible to compatibilise, notably: > >> - Structures now need to inherit from FFIExternalStructure > >> - Arrays now are now shadowed > >> - in general is a bit slower (impossible to compete with ASM) but > in general is not perceptible. > >> - THERE WILL BE BUGS AND NON-IMPLEMENTED FEATURES: Current > implementation is validated with Athens and even Roassal was working, but > of course that does not covers all cases. > >> 2.1) ASMJIT will be removed from system and put in a separated packages. > >> NOTE: There will be a blog post explaining FFI-NB architecture during > the week. > >> > >> 3) There are more or less 70 new failing tests, some of them important > than we need to fix as soon as possible. Please, please, please, help us > with them :) > >> > >> 4) In general we foresee the system will became unstable some weeks, > before it gets back to normal. Please be patient. > >> > >> 5) You will need to adapt your Pharo 5.0 related apps and CI processes > (to take care about new VM). Some programs will stop work at all (for > example, I think Pharo-launcher will need to be adapted). > >> > > > > ah, I forget it! > > > > 6) Some changes to the VM accumulated during the time of transition > (some months now). So, some changes introduced there will not be present in > new VM. I will merge this changes in the next weeks. > > > > cheers! > > Esteban > > >

Dec. 14, 2015

Re: [Pharo-dev] [IMPORTANT] Starting migration to Spur VM

by Guillermo Polito

Thanks! > On 14 dic 2015, at 11:32 a.m., Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 14 Dec 2015, at 11:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> We will start migration to Spur today. >> To complete it, we will require some time, specially to adapt the CI and check everything is ok. >> >> Spur will allow us to do a big step forward in Pharo development, in the concrete you will see it immediately for this: >> - We have noticed a speed increment of 100% in tiny benchmarks (and according to Eliot, it will be at least 35% in general on the system). >> - No more GC stops (noticeable when running large systems) >> - We will be able to scale our systems up to 2G memory consumption without loosing performance. >> >> But, this will have some drawbacks in the first times: >> >> 1) VM will not be compatible between versions anymore: Pharo 5.0 will have a Pharo Spur VM associated (and they are not compatible). >> - There WILL NOT be a "non-spur" version of Pharo 5.0. Once completed the transitions, this will be the only one. >> >> 2) NativeBoost-FFI implementation has been replaced with a new implementation who relies in ThreadedFFIPlugin and IA32Plugin. While we worked a lot to do this transition as painless as possible and we achieve a good level of backward compatibility (most uses of #nbCall: should work out of the box), there are some problems we cannot solve: >> - there are some stuff not possible to compatibilise, notably: >> - Structures now need to inherit from FFIExternalStructure >> - Arrays now are now shadowed >> - in general is a bit slower (impossible to compete with ASM) but in general is not perceptible. >> - THERE WILL BE BUGS AND NON-IMPLEMENTED FEATURES: Current implementation is validated with Athens and even Roassal was working, but of course that does not covers all cases. >> 2.1) ASMJIT will be removed from system and put in a separated packages. >> NOTE: There will be a blog post explaining FFI-NB architecture during the week. >> >> 3) There are more or less 70 new failing tests, some of them important than we need to fix as soon as possible. Please, please, please, help us with them :) >> >> 4) In general we foresee the system will became unstable some weeks, before it gets back to normal. Please be patient. >> >> 5) You will need to adapt your Pharo 5.0 related apps and CI processes (to take care about new VM). Some programs will stop work at all (for example, I think Pharo-launcher will need to be adapted). >> > > ah, I forget it! > > 6) Some changes to the VM accumulated during the time of transition (some months now). So, some changes introduced there will not be present in new VM. I will merge this changes in the next weeks. > > cheers! > Esteban

Dec. 14, 2015

Re: [Pharo-dev] [IMPORTANT] Starting migration to Spur VM

by Esteban Lorenzano

> On 14 Dec 2015, at 11:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > We will start migration to Spur today. > To complete it, we will require some time, specially to adapt the CI and check everything is ok. > > Spur will allow us to do a big step forward in Pharo development, in the concrete you will see it immediately for this: > - We have noticed a speed increment of 100% in tiny benchmarks (and according to Eliot, it will be at least 35% in general on the system). > - No more GC stops (noticeable when running large systems) > - We will be able to scale our systems up to 2G memory consumption without loosing performance. > > But, this will have some drawbacks in the first times: > > 1) VM will not be compatible between versions anymore: Pharo 5.0 will have a Pharo Spur VM associated (and they are not compatible). > - There WILL NOT be a "non-spur" version of Pharo 5.0. Once completed the transitions, this will be the only one. > > 2) NativeBoost-FFI implementation has been replaced with a new implementation who relies in ThreadedFFIPlugin and IA32Plugin. While we worked a lot to do this transition as painless as possible and we achieve a good level of backward compatibility (most uses of #nbCall: should work out of the box), there are some problems we cannot solve: > - there are some stuff not possible to compatibilise, notably: > - Structures now need to inherit from FFIExternalStructure > - Arrays now are now shadowed > - in general is a bit slower (impossible to compete with ASM) but in general is not perceptible. > - THERE WILL BE BUGS AND NON-IMPLEMENTED FEATURES: Current implementation is validated with Athens and even Roassal was working, but of course that does not covers all cases. > 2.1) ASMJIT will be removed from system and put in a separated packages. > NOTE: There will be a blog post explaining FFI-NB architecture during the week. > > 3) There are more or less 70 new failing tests, some of them important than we need to fix as soon as possible. Please, please, please, help us with them :) > > 4) In general we foresee the system will became unstable some weeks, before it gets back to normal. Please be patient. > > 5) You will need to adapt your Pharo 5.0 related apps and CI processes (to take care about new VM). Some programs will stop work at all (for example, I think Pharo-launcher will need to be adapted). > ah, I forget it! 6) Some changes to the VM accumulated during the time of transition (some months now). So, some changes introduced there will not be present in new VM. I will merge this changes in the next weeks. cheers! Esteban

Dec. 14, 2015

[IMPORTANT] Starting migration to Spur VM

by Esteban Lorenzano

We will start migration to Spur today. To complete it, we will require some time, specially to adapt the CI and check everything is ok. Spur will allow us to do a big step forward in Pharo development, in the concrete you will see it immediately for this: - We have noticed a speed increment of 100% in tiny benchmarks (and according to Eliot, it will be at least 35% in general on the system). - No more GC stops (noticeable when running large systems) - We will be able to scale our systems up to 2G memory consumption without loosing performance. But, this will have some drawbacks in the first times: 1) VM will not be compatible between versions anymore: Pharo 5.0 will have a Pharo Spur VM associated (and they are not compatible). - There WILL NOT be a "non-spur" version of Pharo 5.0. Once completed the transitions, this will be the only one. 2) NativeBoost-FFI implementation has been replaced with a new implementation who relies in ThreadedFFIPlugin and IA32Plugin. While we worked a lot to do this transition as painless as possible and we achieve a good level of backward compatibility (most uses of #nbCall: should work out of the box), there are some problems we cannot solve: - there are some stuff not possible to compatibilise, notably: - Structures now need to inherit from FFIExternalStructure - Arrays now are now shadowed - in general is a bit slower (impossible to compete with ASM) but in general is not perceptible. - THERE WILL BE BUGS AND NON-IMPLEMENTED FEATURES: Current implementation is validated with Athens and even Roassal was working, but of course that does not covers all cases. 2.1) ASMJIT will be removed from system and put in a separated packages. NOTE: There will be a blog post explaining FFI-NB architecture during the week. 3) There are more or less 70 new failing tests, some of them important than we need to fix as soon as possible. Please, please, please, help us with them :) 4) In general we foresee the system will became unstable some weeks, before it gets back to normal. Please be patient. 5) You will need to adapt your Pharo 5.0 related apps and CI processes (to take care about new VM). Some programs will stop work at all (for example, I think Pharo-launcher will need to be adapted).

Dec. 14, 2015

[pharo-project/pharo-core] 8812a3: 50496

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 8812a3ea1d836dff057c7f915ffc1fed9b473e6b https://github.com/pharo-project/pharo-core/commit/8812a3ea1d836dff057c7f91… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-12-14 (Mon, 14 Dec 2015) Changed paths: A Collections-Sequenceable.package/Interval.class/instance/copying/shuffled.st A Collections-Tests.package/IntervalTest.class/instance/tests/testShuffled.st A OpalCompiler-Core.package/OCASTClosureAnalyzer.class/instance/visiting/visitArgumentNode_.st M OpalCompiler-Core.package/OCASTClosureAnalyzer.class/instance/visiting/visitBlockNode_.st M OpalCompiler-Core.package/OCASTClosureAnalyzer.class/instance/visiting/visitMethodNode_.st A OpalCompiler-Tests.package/OCASTClosureAnalyzerTest.class/instance/testing - variables/testBlockArgumentIsArgumentVariable.st A OpalCompiler-Tests.package/OCASTClosureAnalyzerTest.class/instance/testing - variables/testInlinedBlockArgumentIsArgumentVariable.st A OpalCompiler-Tests.package/OCASTClosureAnalyzerTest.class/instance/testing - variables/testMethodArgumentIsArgumentVariable.st A OpalCompiler-Tests.package/OCOpalExamples.class/instance/examples-variables/exampleForBlockArgument.st A OpalCompiler-Tests.package/OCOpalExamples.class/instance/examples-variables/exampleForInlinedBlockArgument.st A OpalCompiler-Tests.package/OCOpalExamples.class/instance/examples-variables/exampleWithArgument_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50495.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50496.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50495.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50496.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50496 17233 Interval cannot be "shuffled" https://pharo.fogbugz.com/f/cases/17233 17179 Semantic analysis doesnt compute RBArgumentNode instances https://pharo.fogbugz.com/f/cases/17179 http://files.pharo.org/image/50/50496.zip

Dec. 14, 2015