Re: [Pharo-users] Creating the smallest server runtime footprint

I wasn’t clear on which image to retry - the https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-3.2-Minimal/lastSuccessfulBuild/artifact/Pharo-minimal-64.zip one still shows as b

Re: [Pharo-users] Creating the smallest server runtime footprint

2017-07-31 15:28 GMT+02:00 Tim Mackinnon : > Ok (I am reading there is a lot going on for you guys to sort out at the > moment). > > It sounds like a more stable conversion of Pharo 6.1 for 64 bit would be > best to give me a stable platform to run on. > > In that minimal image - what can I rely o

Re: [Pharo-users] Creating the smallest server runtime footprint

Ok (I am reading there is a lot going on for you guys to sort out at the moment). It sounds like a more stable conversion of Pharo 6.1 for 64 bit would be best to give me a stable platform to run on. In that minimal image - what can I rely on to load code (in trying the 7.0 version it seems li

Re: [Pharo-users] Creating the smallest server runtime footprint

H Tim 2017-07-31 15:07 GMT+02:00 Tim Mackinnon : > Hi Pavel - I’m just revisiting a few of your previous messages on minimal > images as I’m trying to get things working again with Pharo 6.1 now that > you guys have rejigged all of the build pipelines. > > I tried a previous suggestion of: > > Fo

Re: [Pharo-users] Creating the smallest server runtime footprint

Hi Pavel - I’m just revisiting a few of your previous messages on minimal images as I’m trying to get things working again with Pharo 6.1 now that you guys have rejigged all of the build pipelines. I tried a previous suggestion of: For Pharo 6: https://ci.inria.fr/pharo/job/Pharo-6.0-Update-St

Re: [Pharo-users] Creating the smallest server runtime footprint

I'm really curious to see how these numbers will changes with Sista because pharo will be to start hot from a Jit point of view. So you will be able to run your app save it and ship it hot with the JIT optimisation already there. On Wed, Jul 19, 2017 at 6:20 PM, Tim Mackinnon wrote: > Hi - I negl

Re: [Pharo-users] Creating the smallest server runtime footprint

Hi - I neglected to mentioned “the catch” with Lambda, next to my results. So on a tiny EC2 instance you get those kinds of results (this is where I measured the numbers of 50ms) - however on Lambda you aren’t entirely clear what hardware its running on - and there are 2 aspects to consider - a

Re: [Pharo-users] Creating the smallest server runtime footprint

Hi tim if you see libraries not separating their tests: you should report it to their authors or to us if this is our mistakes. You can also load the SUnit package. Stef On Mon, Jul 17, 2017 at 8:00 AM, Tim Mackinnon wrote: > Thanks again Pavel - I'll try the 6.0 step 4 or possibly step 5 with

Re: [Pharo-users] Creating the smallest server runtime footprint

> On 19 Jul 2017, at 14:55, Esteban A. Maringolo wrote: > > I don't know how "mainstream" solutions perform on AWS Lambda or EC2, > but this seems really fast to me. 50 ms is great, assuming it bills by > every 100ms, you still have room to perform your computation. Yes, it seems incredibly fas

Re: [Pharo-users] Creating the smallest server runtime footprint

I don't know how "mainstream" solutions perform on AWS Lambda or EC2, but this seems really fast to me. 50 ms is great, assuming it bills by every 100ms, you still have room to perform your computation. Thank you for pursuing this path, it could open a new territory for using Pharo at big scale.

Re: [Pharo-users] Creating the smallest server runtime footprint

Well I’ve been shooting in the dark a bit - but I also left out the sound and display so’s (e.g. -x execlude the following and add back the null so's zip -r --symlinks ../deploy/$LAMBDA_NAME.zip * -x pharo-local/\* \*.sources \*.changes \*.st \*.log */libgit2.* */libSDL2* */B3DAccelerator* *

Re: [Pharo-users] Creating the smallest server runtime footprint

Thanks again Pavel - I'll try the 6.0 step 4 or possibly step 5 with sunit (as many libraries don't separate out their tests). I've also tried leaving out libgit and libsdl2 .so's on my server build and that seems fine too - making me wonder what others I can safely leave out? Sound is a candi

Re: [Pharo-users] Creating the smallest server runtime footprint

If you want to stay with Pharo 6 image, you can try the bootstrapped version of the minimal image: https://ci.inria.fr/pharo/view/6.0-SysConf/job/Pharo-6.0-Step-04-01-ConfigurationOfMinimalPharo/ -- Pavel 2017-07-15 10:33 GMT+02:00 Pavel Krivanek : > Try the Pharo 7 metacello image (=Pharo 7 min

Re: [Pharo-users] Creating the smallest server runtime footprint

Try the Pharo 7 metacello image (=Pharo 7 minimal image that the CI is already converting to 64bit). There should be no problem with STON because whole Pharo is loaded into it using metacello and filetree. Pharo 6 minimal image is done differently (by shrinking) and not so well tested. For the con

Re: [Pharo-users] Creating the smallest server runtime footprint

Hi Pavel - thanks for getting me to the point where I could even have a minimal image. As I’m on the edge of my Pharo knowledge here, I’ll try and run with this as best I can. I’d been using the 6.0 image you suggested to me - but maybe I could use a 70 image with Pharo 6 for a while (until the

Re: [Pharo-users] Creating the smallest server runtime footprint

Hi Tim, you can base the your work on the bootstrapped image, see https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/, file Pharo7.0-core-*.zip This image does not have a lot of basic components like Monticello or network but it has a compiler so the code can be imported as *.st files. The

Re: [Pharo-users] Creating the smallest server runtime footprint

Hi - the script I'm using is in https://gitlab.com/macta/PharoLambda - it's nothing fancy, look at the Gitlab .yml file. This is all Linux running in an ubuntu docker image on Gitlab CI. Tim Sent from my iPhone Sent from my iPhone > On 15 Jul 2017, at 06:27, Hernán Morales Durand > wrote:

Re: [Pharo-users] Creating the smallest server runtime footprint

Hi Tim, 2017-07-14 4:59 GMT-03:00 Tim Mackinnon : > Hi - buoyed by the success of a minimal image (thanks Pavel), I'm > wondering if I can get even smaller. > > Can you share a script to reproduce the steps to build a minimal image? Is it reproducible under Windows? Cheers, Hernán

Re: [Pharo-users] Creating the smallest server runtime footprint

On Fri, Jul 14, 2017 at 09:06:44AM +0100, Tim Mackinnon wrote: > Related to this question - in the Linux vm there are several .so files that > have numerical extensions as well as the same named .so file. Are these merge > conflicts or platform variations of the same files? > > libSDL2-2.0.so.0.4.

Re: [Pharo-users] Creating the smallest server runtime footprint

Related to this question - in the Linux vm there are several .so files that have numerical extensions as well as the same named .so file. Are these merge conflicts or platform variations of the same files? E.g. libSDL2-2.0.so.0.4.1 & libSDL2-2.0.so & libSDL2.so Are all in there? Tim Sent fr

[Pharo-users] Creating the smallest server runtime footprint

Hi - buoyed by the success of a minimal image (thanks Pavel), I'm wondering if I can get even smaller. There are lots of .so's in the vm which wouldn't make sense on a server once deployed - sound, maybe libgit ... Is there a list of the essential ones, or tips on what I can strip out of the L