June 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] pharo bash script with startup

by JuliÃ¡n Maestri

Try with ./pharo or try with an absolute image path. On Wed, Jun 27, 2018, 04:03 Tim Mackinnon <tim(a)testit.works> wrote: > Iâve not noticed that problem on ubuntu or AWS lambda so there must be > something different going on. > > Sent from my iPhone > > On 27 Jun 2018, at 07:30, Otto Behrens <otto(a)finworks.biz> wrote: > > Hi, > > I just installed pharo 6.1 using the .zip file ( > http://files.pharo.org/platform/Pharo6.1-64-linux.zip) and battled to > start up pharo with arguments. > > The issue is that the pharo bash script (in the extracted home dir) quotes > all arguments: > > # execute > exec "$LINUX/pharo" \ > --plugins "$LINUX" \ > --encoding utf8 \ > -vm-display-X11 \ > "$image" > > where > > image = $* > > The impact is that if I want to run a startup script, eg. > > pharo my.image startup.st > > pharo complains with "Could not open the Pharo image file: 'my.image > startup.st' > > So I must run the executable directly? > > If so, some questions about the options that the bash script passes in: > --plugins "$LINUX" is this necessary? will the default not be enough? > --encoding utf8 the usage output says for example --textenc > default is "UTF-8". Is utf8 the same thing? > -vm-display-X11 I tried starting without this, and it worked. Do I > need to explicitly start with this? > > Thanks > Otto > >

June 27, 2018

Re: [Pharo-users] pharo bash script with startup

by Tim Mackinnon

Iâve not noticed that problem on ubuntu or AWS lambda so there must be something different going on. Sent from my iPhone > On 27 Jun 2018, at 07:30, Otto Behrens <otto(a)finworks.biz> wrote: > > Hi, > > I just installed pharo 6.1 using the .zip file (http://files.pharo.org/platform/Pharo6.1-64-linux.zip) and battled to start up pharo with arguments. > > The issue is that the pharo bash script (in the extracted home dir) quotes all arguments: > > # execute > exec "$LINUX/pharo" \ > --plugins "$LINUX" \ > --encoding utf8 \ > -vm-display-X11 \ > "$image" > > where > > image = $* > > The impact is that if I want to run a startup script, eg. > > pharo my.image startup.st > > pharo complains with "Could not open the Pharo image file: 'my.image startup.st' > > So I must run the executable directly? > > If so, some questions about the options that the bash script passes in: > --plugins "$LINUX" is this necessary? will the default not be enough? > --encoding utf8 the usage output says for example --textenc default is "UTF-8". Is utf8 the same thing? > -vm-display-X11 I tried starting without this, and it worked. Do I need to explicitly start with this? > > Thanks > Otto

June 27, 2018

pharo bash script with startup

by Otto Behrens

Hi, I just installed pharo 6.1 using the .zip file ( http://files.pharo.org/platform/Pharo6.1-64-linux.zip) and battled to start up pharo with arguments. The issue is that the pharo bash script (in the extracted home dir) quotes all arguments: # execute exec "$LINUX/pharo" \ --plugins "$LINUX" \ --encoding utf8 \ -vm-display-X11 \ "$image" where image = $* The impact is that if I want to run a startup script, eg. pharo my.image startup.st pharo complains with "Could not open the Pharo image file: 'my.image startup.st' So I must run the executable directly? If so, some questions about the options that the bash script passes in: --plugins "$LINUX" is this necessary? will the default not be enough? --encoding utf8 the usage output says for example --textenc default is "UTF-8". Is utf8 the same thing? -vm-display-X11 I tried starting without this, and it worked. Do I need to explicitly start with this? Thanks Otto

June 27, 2018

Re: [Pharo-users] Microservices using Pharo

by Torsten Bergmann

Hi Andrei, I guess there is no definitive answer - it highly depends on your microservice itself and what it does with other backends (database, other services) - If you run on Seaside with state then this might be interesting: http://onsmalltalk.com/scaling-seaside If you want to scale then stateful might not be the best way to go - this is not different from other web technologies. - I prefer the REST and stateless approach, several images with a fast balancer at the front (nginx) This is a pattern you more often see in web development as usually - the client side is written in JavaScript as single page app (SPA) or progressive web app (PWA) - and server side provides a stateless REST API (which opens your application not only to human users using the SPA/PWA but also to other programs and services using the API) You can easily provide REST API with Seaside-REST package, with Teapot or with Tealight (an addition I wrote to Teapot). Follow the guide for Tealight, especially the last part here: https://github.com/astares/Tealight - Allstocker.com is running with just 2 images and nginx, see the details here https://pharoweekly.wordpress.com/2016/10/17/allstocker-internals/ - The enterprise book has some guidance too https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… I recommend to make a technical prototype, test and measure. Balancing and scaling is not different from other technologies (Java, PHP, NodeJS, ...) and there are many tutorials out there for this part. Think about container technologies and virtualization (for cloud or other). Played with Pharo on docker - very easy to setup. I summarized my findings in a new "Pharo and docker" tutorial on http://wiki.astares.com/pharo/613 Hope some of this helps! Bye Torsten

June 27, 2018

Re: [Pharo-users] Microservices using Pharo

by JuliÃ¡n Maestri

At work we're using some microservices in pharo, implemented with Zink and Teapot, can't tell you much about performance because they are not being stress tested currently. I'm using Traefik as a load balancer WITH sticky session on docker, mainly because it scales acording to the docker configuration (traefik can detect new docker instances and add them to the load balancer group) https://docs.traefik.io/configuration/backends/docker/ To keep images running we use a docker swarm which is in charge of restarting them if they fail. Why? ease of use, it's easier to deploy and keep track of what is where. https://docs.docker.com/engine/swarm/ For the Pharo docker image i'm running one based on debian slim, with the VM for Pharo 6.1 (32 bit). Code in https://github.com/ba-st/docker-pharo, available in the docker registry as basmalltalk/pharo:6.1 <https://hub.docker.com/r/basmalltalk/pharo/> As i have no need for the sources file and removing it reduces the final image size it's removed, but you can add it (or prevent it's removal if you need) If you need help with any of these, please ask (if it's urgent send me a direct mail, i don't read the Pharo list very often). On 27 June 2018 at 02:42, jtuchel(a)objektfabrik.de <jtuchel(a)objektfabrik.de> wrote: > Norbert, > > Am 26.06.18 um 21:41 schrieb Norbert Hartl: > > > > Am 26.06.2018 um 20:44 schrieb Andrei Stebakov <lispercat(a)gmail.com>: > > What would be an example for load balancer for Pharo images? Can we run > multiple images on the same server or for the sake of balancing > configuration we can only run one image per server? > > There are a lot of possibilities. You can start multiple images on > different ports and use nginx with an upstream rule to load balance. I > would recommend using docker for spawning multiple images on a host. Again > with nginx as frontend load balancer. The point is that you can have at > least twice as muh inages running then you have CPU cores. And of course a > lot more. > > > the last time I checked nginx, the load balancing and sticky session stuff > was not available in the free edition. So I guess you either pay for nginx > (which I think is good) or you know some free 3d party addons... > > I wonder what exactly the benefit of Docker is in that game? On our > servers we run 10 images on 4 cores with HT (8 virtual cores) and very > rareley have real performance problems. We use Glorp, so there is a lot of > SQL queriing going on for quite basic things already. So my guess would be > that your "2 images per core" are conservative and leave air for even a > third one, depending on all the factors already discussed here. > > What's not to underestimate is all the stuff around monitoring and > restarting images when things go wrong, but that's another story... > > Joachim > > > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de <jtuchel(a)objektfabrik.de> > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > > >

June 27, 2018

Re: [Pharo-users] Microservices using Pharo

by jtuchel＠objektfabrik.de

Norbert, Am 26.06.18 um 21:41 schrieb Norbert Hartl: > > > Am 26.06.2018 um 20:44 schrieb Andrei Stebakov <lispercat(a)gmail.com > <mailto:lispercat@gmail.com>>: > >> What would be an example for load balancer for Pharo images? Can we >> run multiple images on the same server or for the sake of balancing >> configuration we can only run one image per server? >> > There are a lot of possibilities. You can start multiple images on > different ports and use nginx with an upstream rule to load balance. I > would recommend using docker for spawning multiple images on a host. > Again with nginx as frontend load balancer. The point is that you can > have at least twice as muh inages running then you have CPU cores. And > of course a lot more. > the last time I checked nginx, the load balancing and sticky session stuff was not available in the free edition. So I guess you either pay for nginx (which I think is good) or you know some free 3d party addons... I wonder what exactly the benefit of Docker is in that game? On our servers we run 10 images on 4 cores with HT (8 virtual cores) and very rareley have real performance problems. We use Glorp, so there is a lot of SQL queriing going on for quite basic things already. So my guess would be that your "2 images per core"Â are conservative and leave air for even a third one, depending on all the factors already discussed here. What's not to underestimate is all the stuff around monitoring and restarting images when things go wrong, but that's another story... Joachim -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1Â Â Â Â Â Â Â Â Â Â Â Â Â http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0Â Â Â Â Â Fax: +49 7141 56 10 86 1

June 27, 2018

Re: [Pharo-users] Microservices using Pharo

by jtuchel＠objektfabrik.de

Am 26.06.18 um 20:47 schrieb Andrei Stebakov: > I guess for multiple images on the same server we need to spawn off > images listening on different ports. > exactly. We use Apache mod_proxy_balancer with sticky sessions for our configuration. The sticky session part is important if you use Seaside (share everything approach with state living on the server). We do have problems with mod_proxy_balancer when an image gets stuck, because it is not actively monitoring its backends, so there are better options out there that we need to investigate once we havetime. Luckily, our Smalltalk images turn put to be very stable, the bottleneck being DB2 (surprisingly). Joachim -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1Â Â Â Â Â Â Â Â Â Â Â Â Â http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0Â Â Â Â Â Fax: +49 7141 56 10 86 1

June 27, 2018

Re: [Pharo-users] copy & paste

by Otto Behrens

> > > The stable version on opensuse is quite old. And apparently not 6.1. > > So, does this sadly mean that the paragraph on the top of the page > > "Zip file" is updated, but the rest of the page not? > > Very likely, as the Zip packager (human) is probable not the Suse > packager (another human) > > Does the zip package work for you? > I prefer to use the deb package because I make it part of my ubuntu installation. Does this mean that even the .zip package could be old? I would just like to generally say that this could influence how people out there see Pharo. If a newbie tries it out, he or she may just get stuck with stupid things like this copy & paste (by trying to copy an example from the Pharo site), only to realise that this is an old version. It gives the impression that the "stable" version is not stable. Old campaigners like me might persist, but most people will give up right here. I think I should revert to the .zip.

June 27, 2018

Re: [Pharo-users] [Dynabook][Morphic][TLM][Geometry] Re: [ANN] GNU Dr. Geo release 18.06

by Hilaire

As I am only reading this list throught Gname newsgroup I can't read the senders' email, so please email me at hilaire [at] drgeo.eu so we can engage a private conversation Hilaire Le 26/06/2018 Ã 05:41, H. Hirzel a Ã©critÂ : > This message is off-list as I do not have the capacity NOW to > maintain a conversation on this list. -- Dr. Geo http://drgeo.eu

June 26, 2018

Re: [Pharo-users] copy & paste

by Hilaire

Le 26/06/2018 Ã 05:48, Otto Behrens a Ã©critÂ : > > > We use the package installation for ubuntu described > here:Â https://pharo.org/gnu-linux-installation-64. > > The stable version on opensuse is quite old. And apparently not 6.1. > So, does this sadly mean that the paragraph on the top of the page > "Zip file" is updated, but the rest of the page not? Very likely, as the Zip packager (human) is probable not the Suse packager (another human) Does the zip package work for you? Hilaire -- Dr. Geo http://drgeo.eu

June 26, 2018