Different versions of Moose 6.0
by Serge Stinckwich
Dear all,
apparently Moose 6.0 version available on the website:
http://www.moosetechnology.com/
is not the same version used on SmalltalkCI.
1st one is :
Pharo5.0 Latest update: #50761
and the other one:
Pharo5.0 Latest update: #50770
Is it possible to have same version on both sides ? :-)
Because we have some code that only fails on the CI and this source of
confusion.
Regards,
--
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/
6 years
Re: [Pharo-dev] Growing large images: the case of Moose models
by Blondeau Vincent
Thanks Eliot for the implementation of the new compactor!
Just to add a piece of information: the mse imported have a size of 40Mb.
Cheers,
Vincent
De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Clément Bera
Envoyé : vendredi 3 mars 2017 11:56
À : Discusses Development of Pharo
Objet : [Pharo-dev] Growing large images: the case of Moose models
Hello everyone,
This morning I investigated with Vincent Blondeau a problem reported by the Moose community a while ago: loading Moose model is slower in Spur (Pharo 5+) than in pre-Spur (Pharo 4 and older). In general, this problem was present for anyone growing images to a significant size.
To investigate the problem, we loaded a 200Mb[3] Moose model on a 250Mb image, growing the image to 450Mb. Loading such a model takes 2 minutes in Spur and 1m30s in pre-Spur VMs.
Using the stable Pharo VM, the analysis results were the following:
- total time spent to load the Model: 2 minutes
- time spent in full GC: 1 minute (4 fullGCs)
- time spent in scavenges[1]: 15 seconds
On the 2 minutes spent, we have 50% of the time spent in full GCs, 12.5% in scavenges, 37.5% executing code.
We then used the latest VM that features the new compactor (VM from beginning of March 2017 and over). The full GC execution time went down from 1 minute to 2 seconds.
In addition, we increased the size of Eden[2] from 4Mb to 12Mb. Time spent in scavenges decreased from 15 seconds to 5 seconds.
Overall, loading the model is now taking ~50 seconds instead of 2 minutes.
To increase Eden size, one needs to run a script similar to:
| currentEdenSize desiredEdenSize |
currentEdenSize := Smalltalk vm parameterAt: 44.
desiredEdenSize := currentEdenSize * 4.
Smalltalk vm parameterAt: 45 put: desiredEdenSize.
And then restart the image.
I hope this report can be useful for some of you. I will try to make a blog post out of it, detailing other GC settings one can change from the image to improve performance.
Best,
Clement
[1] A scavenge is basically the garbage collection of only young objects
[2] Eden is basically the space where objects are initially allocated.
[3] All numbers in the report are order of magnitudes and not precise numbers
!!!*************************************************************************************
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
6 years
Segmentation fault on Moose 6.1 Build
by Blondeau Vincent
Hi,
The latest builds of the Moose6.1 image are failing due to a segmentation fault.
Here is the link to the last build: https://ci.inria.fr/moose/job/moose-6.1/550/console
How can we fix this?
Thanks in advance,
Cheers,
Vincent
!!!*************************************************************************************
"Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
6 years
Re: [Pharo-dev] Re: Segmentation fault on Moose 6.1 Build
by Tudor Girba
Hmm, it looks like something changed and the build is now yellow.
Does anyone have the time to check this mysterious behavior?
Cheers,
Doru
> On Mar 2, 2017, at 1:24 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote:
>
> I will try to make some easier way to reproduce it and open an issue
>
> -- Pavel
>
> 2017-03-02 11:58 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>:
> Hm, I haven't check the time of the failing build... Yes, it will be related...
>
> 2017-03-02 11:51 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>:
> Except for tiny changes in Athens in 60419 :)
>
> Doru
>
>
> > On Mar 2, 2017, at 11:33 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote:
> >
> > On image side nothing relevant happened in 60418 where it started to fail.
> >
> > -- Pavel
> >
> > 2017-03-02 11:31 GMT+01:00 Blondeau Vincent <vincent.blondeau(a)worldline.com>:
> > I heard that the gc compactor have changed.
> >
> > Cheers,
> > Vincent
> >
> > > -----Message d'origine-----
> > > De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] De la part de
> > > Tudor Girba
> > > Envoyé : jeudi 2 mars 2017 11:29
> > > À : Pharo Development List
> > > Cc : Moose-related development
> > > Objet : [Moose-dev] Re: [Pharo-dev] Segmentation fault on Moose 6.1 Build
> > >
> > > Hi,
> > >
> > > Was there a change related to the stable VM?
> > >
> > > Cheers,
> > > Doru
> > >
> > >
> > > > On Mar 2, 2017, at 11:23 AM, Blondeau Vincent
> > > <vincent.blondeau(a)worldline.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > The latest builds of the Moose6.1 image are failing due to a segmentation
> > > fault.
> > > > Here is the link to the last build:
> > > > https://ci.inria.fr/moose/job/moose-6.1/550/console
> > > >
> > > > How can we fix this?
> > > >
> > > > Thanks in advance,
> > > >
> > > > Cheers,
> > > > Vincent
> > > >
> > > >
> > > >
> > > !!!********************************************************
> > > ***********
> > > > ****************** "Ce message et les pièces jointes sont
> > > > confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut
> > > également être protégé par le secret professionnel. Si vous recevez ce
> > > message par erreur, merci d'en avertir immédiatement l'expéditeur et de le
> > > détruire. L'intégrité du message ne pouvant être assurée sur Internet, la
> > > responsabilité de Worldline ne pourra être recherchée quant au contenu de
> > > ce message. Bien que les meilleurs efforts soient faits pour maintenir cette
> > > transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à
> > > cet égard et sa responsabilité ne saurait être recherchée pour tout dommage
> > > résultant d'un virus transmis.
> > > >
> > > > This e-mail and the documents attached are confidential and intended
> > > solely for the addressee; it may also be privileged. If you receive this e-mail in
> > > error, please notify the sender immediately and destroy it. As its integrity
> > > cannot be secured on the Internet, the Worldline liability cannot be triggered
> > > for the message content. Although the sender endeavours to maintain a
> > > computer virus-free network, the sender does not warrant that this
> > > transmission is virus-free and will not be liable for any damages resulting
> > > from any virus transmitted.!!!"
> > > > <dump.txt>
> > >
> > > --
> > > www.tudorgirba.com
> > > www.feenk.com
> > >
> > > “Live like you mean it."
> > >
> > > _______________________________________________
> > > Moose-dev mailing list
> > > Moose-dev(a)list.inf.unibe.ch
> > > https://www.list.inf.unibe.ch/listinfo/moose-dev
> >
> > !!!*************************************************************************************
> > "Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
> >
> > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
> >
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "Yesterday is a fact.
> Tomorrow is a possibility.
> Today is a challenge."
>
>
>
>
>
>
>
--
www.tudorgirba.com
www.feenk.com
"Beauty is where we see it."
6 years
Google Summer of Code 2017: Call for students for Pharo Consortium
by Serge Stinckwich
*** Please forward this message to students that might be interested ***
Heartiest Congratulations !
Pharo Consortium has been selected as a mentor organisation for Google
Summer of Code 2017.
Google Summer of Code is a global program focused on introducing
students to open source software development.
Students work on a 3 month programming project with an open source
organisation during their break from university.
Read more at https://summerofcode.withgoogle.com/
Pharo is a pure object-oriented programming language and a powerful
environment, focused on simplicity and immediate feedback (think IDE
and OS rolled into one).
Everything in Pharo is an object. The entire syntax of Pharo fits on a
postcard coding can be done directly in the debugger. Pharo has super
cool tools that empower you and make you super efficient. Pharo's goal
is to deliver a clean, innovative, free and open-source immersive
environment. By providing a stable and small core system, excellent
developing tools, and maintained releases, Pharo is an attractive
platform to build and deploy mission critical applications. Pharo
fosters a healthy ecosystem of both private and commercial
contributors who advance and maintain the core system and its external
packages.
More information about Pharo is available here: http://www.pharo.org/
We invite all the prospective eligible students to code their summer
away with Pharo Consortium.
Student Responsibilities
...to your Mentor
- Submit quality work
- Regularly communicate work completed, what you intend to do next, and blockers
- Ask for help when something is preventing you from achieving a goal
- Give indication that you are alive and working daily (GSoC)
- Re-evaluate work scope when significantly ahead of expectations (GSoC)
- Communicate with your mentor AND the broader community
- Inform when work capacity will be reduced, as early as possible
(e.g., family, health, other work) (GSoC)
- Listen and respond to feedback
...to the Org Admin
Let them know when there are
- Interaction issues with any mentor or community member
- Significant disagreements involving your work or changes to your work plan
Read more about responsibilities here:
https://developers.google.com/open-source/gsoc/help/responsibilities
Hence, we invite enthusiastic student developers contributors to work
with Pharo Consortium for GSoC 2017.
1. A first list of projects are available here :
http://gsoc.pharo.org/ but more can be found by interacting with
mentors from the Pharo community.
2. Join dedicated channels, #gsoc-students for general interactions
with students on Pharo slack. In order to get an invitation for
pharoproject.slack.com visit the URL here:
http://slackinvites.pharo.org/
Discuss with mentors about the complexity and skills required for the
different projects.
3. Please help fix bugs, open relevant issues, suggest changes,
additional features, help build a roadmap, and interact with mentors
on mailing list and/or slack to get a better insight into projects.
Better the contributions, Better are the chances of selection.
Before applying:
* Knowledge about OOP
* Basic idea about Pharo & Smalltalk syntax and ongoing projects
* Past experience with Pharo & Smalltalk
* Interaction with organisation
You can start with the Pharo MOOC : http://files.pharo.org/mooc/
Guidelines for Proposal:
* Introduction: Clearly defined problem. Current state of things.
Issues you wish to solve and why. Conclude with solution.
* Project goals: Format it like a list. Propose a clear list of
deliverables, explaining exactly what you promise to do and what you
do not plan to do. “Future developments” can be mentioned. It is
better to promise less and deliver more than to promise a lot and then
fall short.
* Implementation: Longer and more detailed. Provide technical details,
show that you understand the technology and illustrate key technical
elements of your proposed solution.
* Timeline: Make it weekly. Set goals for each week. Be upfront about
other commitments, including exams, classes, travel, internships,
jobs, etc.
* Benefits to Community: Make your case a benefit to the organization.
* Related Work: Research and write how the project fits into the
target organization. Explain related works, similarities &
differences.
* About me: Provide full contact information, email addresses,
websites, IRC nick, postal address and telephone. Write a few
sentences about yourself, previous experiences and why you think
you’re the best for this job.
Submit your proposal early. Keep it short. Include necessary
information. Get it reviewed in the mailing list or Slack channel
before submitting it.
The deadline for submitting your proposal is March 20th to April 3rd
on https://summerofcode.withgoogle.com/
Looking forward to great talent joining our organisation this summer.
Warm Regards
Pharo Organisation Admins
(Alexandre Bergel, Jigyasa Grover, Serge Stinckwich & Yuriy Tymchuk)
6 years