- Pharo-users - lists.pharo.org

Re: [Pharo-users] Thread-safe initialization of class state (was Re: Threads safety in Pharo)

by Tim Mackinnon

Interesting, your example was subtle enough that I had to read it a few times to understand the issue. (I was caught up on the ifNil and not the contents). Actually, thinking about it - isn't the real issue the #ifNil - you want an atomic version. It strikes me you could wrap the whole concept into something like an AtomicLazyVariable? E.g. initialise fileTypes := AtomicLazyVariable using: [ Dictionary new at: 'txt' put: 'Text File'; at: 'html' put: 'Web Page'; yourself ]. Then have something fileTypes ^fileTypes value Where you have a critical section in #value? Tim Sent from my iPhone > On 11 Aug 2017, at 07:53, monty <monty2(a)programmer.net> wrote: > > Here's a hypothetical broken class method that does lazy initialization of a class inst var: > > fileTypes > fileTypes ifNil: [ > fileTypes := Dictionary new. > fileTypes > at: 'txt' put: 'Text File'; > at: 'html' put: 'Web Page'; > at: 'pdf' put: 'Portable Document Format File'; > at: 'doc' put: 'Microsoft Word Document']. > ^ fileTypes. > > Because the assignment is done first and the initialization is done after with a cascade of interruptable sends of #at:put:, there's a window after the assignment where 'fileTypes' is not nil but also not fully initialized--a race condition. > > The fix is simple. Do the initialization before the atomic assignment takes place, so the var is only ever bound to nil or a fully initialized object: > > fileTypes > fileTypes ifNil: [ > fileTypes := > Dictionary new > at: 'txt' put: 'Text File'; > at: 'html' put: 'Web Page'; > at: 'pdf' put: 'Portable Document Format File'; > at: 'doc' put: 'Microsoft Word Document'; > yourself]. > ^ fileTypes. > > The fixed code is still vulnerable to duplicate initialization, because the initialization sequence is interruptable and 'fileTypes' is nil during it, but as long as the initialization is cheap enough, has no side effects that restrict how often it can be done, and it's enough that the initialized objects are equal (but not identical), that's OK. > > If it's too complex for a single statement, you can use a temp vars or put it in a separate factory method: > > fileTypes > fileTypes ifNil: [ > fileTypes := self newFileTypes]. > ^ fileTypes. > > Similar precautions (given how easy) might as well be taken with explicit initialization of class state too. Of course if the object is mutated later (in other methods), then Mutexes or other constructs are needed to guard access. But for immutable class state, ensuring initialization is done before assignment should be enough. > >> Sent: Tuesday, August 01, 2017 at 7:36 AM >> From: "Stephane Ducasse" <stepharo.self(a)gmail.com> >> To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> >> Subject: Re: [Pharo-users] Threads safety in Pharo >> >> I would love to have an analysis of assumptions made in some code. >> Because my impression is that the concurrent code is sometimes defined >> knowing the underlying logic of scheduler and this is not good. >> As I said to abdel privately in french it would be great to start from >> my french squeak book (Yes I wrote one long time ago) chapter on >> concurrent programming and turn it into a pharo chapter. >> >> Stef >> >>> On Tue, Aug 1, 2017 at 1:31 PM, Ben Coman <btc(a)openinworld.com> wrote: >>> Not sure I'll have what you're looking for, but to start, do you mean >>> Pharo's green threads or vm native threads? >>> cheers -ben >>> >>> On Mon, Jul 31, 2017 at 7:38 AM, Alidra Abdelghani via Pharo-users >>> <pharo-users(a)lists.pharo.org> wrote: >>>> >>>> >>>> >>>> ---------- Forwarded message ---------- >>>> From: Alidra Abdelghani <alidrandco(a)yahoo.fr> >>>> To: pharo-users(a)lists.pharo.org >>>> Cc: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr>, farid arfi >>>> <arfi_f(a)hotmail.com> >>>> Bcc: >>>> Date: Mon, 31 Jul 2017 01:38:58 +0200 >>>> Subject: Threads safety in Pharo >>>> Hi, >>>> >>>> Somebody once evoked the problem of threads safety in Pharo. With a friend >>>> of mine who is expert in formal methods and process scheduling, we would >>>> like to have a look on it. >>>> Does anyone knows a good document describing the problem of Pharo with >>>> threads safety or at least any document that we can start with? >>>> >>>> Thanks in advance, >>>> Abdelghani >>>> >>>> >>>> >>> >> >

Aug. 11, 2017

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

by Denis Kudriashov

This is cool Tim. So what image size you deployed at the end? 2017-08-10 15:47 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > I just wanted to thank everyone for their help in getting my pet project > further along, so that now I can announce that PharoLambda is now working > with the V7 minimal image and also supports post mortem debugging by saving > a zipped fuel context onto S3. > > This latter item is particularly satisfying as at a recent serverless > conference (JeffConf) there was a panel where poor development tools on > serverless platforms was highlighted as a real problem. > > In our community weâve had these kinds of tools at our fingertips for ages > - but I donât think the wider development community has really noticed. > Debugging something short lived like a Lambda execution is quite startling, > as the current answer is âadd more loggingâ, and we all know that sucks. To > this end, Iâve created a little screencast showing this in action - and it > was pretty cool because it was a real example I encountered when I got > everything working and was trying my test application out. > > Iâve also put a bit of work into tuning the excellent GitLab CI tools, so > that I can cache many of the artefacts used between different build runs > (this might also be of interest to others using CI systems). > > The Gitlab project is on: https://gitlab.com/macta/PharoLambda > And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E > > Tim > > > On 15 Jul 2017, at 00:39, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - Iâve been playing around with getting Pharo to run well on AWS > Lambda. Itâs early days, but I though it might be interesting to share what > Iâve learned so far. > > Usage examples and code at https://gitlab.com/macta/PharoLambda > > With help from many of the folks here, Iâve been able to get a simple > example to run in 500ms-1200ms with a minimal Pharo 6 image. You can easily > try it out yourself. This seems slightly better than what the GoLang folks > have been able to do. > > Tim > > >

Aug. 11, 2017

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

by Tudor Girba

+1 Doru > On Aug 10, 2017, at 11:34 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Tim > > I definitively think that we could turn it into a Pharo success story > or something that we can keep on the web site > because it is really nice. > > Stef > > On Thu, Aug 10, 2017 at 3:47 PM, Tim Mackinnon <tim(a)testit.works> wrote: >> I just wanted to thank everyone for their help in getting my pet project >> further along, so that now I can announce that PharoLambda is now working >> with the V7 minimal image and also supports post mortem debugging by saving >> a zipped fuel context onto S3. >> >> This latter item is particularly satisfying as at a recent serverless >> conference (JeffConf) there was a panel where poor development tools on >> serverless platforms was highlighted as a real problem. >> >> In our community weâve had these kinds of tools at our fingertips for ages - >> but I donât think the wider development community has really noticed. >> Debugging something short lived like a Lambda execution is quite startling, >> as the current answer is âadd more loggingâ, and we all know that sucks. To >> this end, Iâve created a little screencast showing this in action - and it >> was pretty cool because it was a real example I encountered when I got >> everything working and was trying my test application out. >> >> Iâve also put a bit of work into tuning the excellent GitLab CI tools, so >> that I can cache many of the artefacts used between different build runs >> (this might also be of interest to others using CI systems). >> >> The Gitlab project is on: https://gitlab.com/macta/PharoLambda >> And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E >> >> Tim >> >> >> On 15 Jul 2017, at 00:39, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - Iâve been playing around with getting Pharo to run well on AWS Lambda. >> Itâs early days, but I though it might be interesting to share what Iâve >> learned so far. >> >> Usage examples and code at https://gitlab.com/macta/PharoLambda >> >> With help from many of the folks here, Iâve been able to get a simple >> example to run in 500ms-1200ms with a minimal Pharo 6 image. You can easily >> try it out yourself. This seems slightly better than what the GoLang folks >> have been able to do. >> >> Tim >> >> > -- www.tudorgirba.com www.feenk.com "Reasonable is what we are accustomed with."

Aug. 11, 2017

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

by Tudor Girba

Very nice work, Tim! It is quite impressive what you could do within a short amount of time (essentially since PharoDays). Please do keep this up. Cheers, Doru > On Aug 10, 2017, at 3:47 PM, Tim Mackinnon <tim(a)testit.works> wrote: > > I just wanted to thank everyone for their help in getting my pet project further along, so that now I can announce that PharoLambda is now working with the V7 minimal image and also supports post mortem debugging by saving a zipped fuel context onto S3. > > This latter item is particularly satisfying as at a recent serverless conference (JeffConf) there was a panel where poor development tools on serverless platforms was highlighted as a real problem. > > In our community weâve had these kinds of tools at our fingertips for ages - but I donât think the wider development community has really noticed. Debugging something short lived like a Lambda execution is quite startling, as the current answer is âadd more loggingâ, and we all know that sucks. To this end, Iâve created a little screencast showing this in action - and it was pretty cool because it was a real example I encountered when I got everything working and was trying my test application out. > > Iâve also put a bit of work into tuning the excellent GitLab CI tools, so that I can cache many of the artefacts used between different build runs (this might also be of interest to others using CI systems). > > The Gitlab project is on: https://gitlab.com/macta/PharoLambda > And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E > > Tim > > >> On 15 Jul 2017, at 00:39, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - Iâve been playing around with getting Pharo to run well on AWS Lambda. Itâs early days, but I though it might be interesting to share what Iâve learned so far. >> >> Usage examples and code at https://gitlab.com/macta/PharoLambda >> >> With help from many of the folks here, Iâve been able to get a simple example to run in 500ms-1200ms with a minimal Pharo 6 image. You can easily try it out yourself. This seems slightly better than what the GoLang folks have been able to do. >> >> Tim > -- www.tudorgirba.com www.feenk.com "Quality cannot be an afterthought."

Aug. 11, 2017

Thread-safe initialization of class state (was Re: Threads safety in Pharo)

by monty

Here's a hypothetical broken class method that does lazy initialization of a class inst var: fileTypes fileTypes ifNil: [ fileTypes := Dictionary new. fileTypes at: 'txt' put: 'Text File'; at: 'html' put: 'Web Page'; at: 'pdf' put: 'Portable Document Format File'; at: 'doc' put: 'Microsoft Word Document']. ^ fileTypes. Because the assignment is done first and the initialization is done after with a cascade of interruptable sends of #at:put:, there's a window after the assignment where 'fileTypes' is not nil but also not fully initialized--a race condition. The fix is simple. Do the initialization before the atomic assignment takes place, so the var is only ever bound to nil or a fully initialized object: fileTypes fileTypes ifNil: [ fileTypes := Dictionary new at: 'txt' put: 'Text File'; at: 'html' put: 'Web Page'; at: 'pdf' put: 'Portable Document Format File'; at: 'doc' put: 'Microsoft Word Document'; yourself]. ^ fileTypes. The fixed code is still vulnerable to duplicate initialization, because the initialization sequence is interruptable and 'fileTypes' is nil during it, but as long as the initialization is cheap enough, has no side effects that restrict how often it can be done, and it's enough that the initialized objects are equal (but not identical), that's OK. If it's too complex for a single statement, you can use a temp vars or put it in a separate factory method: fileTypes fileTypes ifNil: [ fileTypes := self newFileTypes]. ^ fileTypes. Similar precautions (given how easy) might as well be taken with explicit initialization of class state too. Of course if the object is mutated later (in other methods), then Mutexes or other constructs are needed to guard access. But for immutable class state, ensuring initialization is done before assignment should be enough. > Sent: Tuesday, August 01, 2017 at 7:36 AM > From: "Stephane Ducasse" <stepharo.self(a)gmail.com> > To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] Threads safety in Pharo > > I would love to have an analysis of assumptions made in some code. > Because my impression is that the concurrent code is sometimes defined > knowing the underlying logic of scheduler and this is not good. > As I said to abdel privately in french it would be great to start from > my french squeak book (Yes I wrote one long time ago) chapter on > concurrent programming and turn it into a pharo chapter. > > Stef > > On Tue, Aug 1, 2017 at 1:31 PM, Ben Coman <btc(a)openinworld.com> wrote: > > Not sure I'll have what you're looking for, but to start, do you mean > > Pharo's green threads or vm native threads? > > cheers -ben > > > > On Mon, Jul 31, 2017 at 7:38 AM, Alidra Abdelghani via Pharo-users > > <pharo-users(a)lists.pharo.org> wrote: > >> > >> > >> > >> ---------- Forwarded message ---------- > >> From: Alidra Abdelghani <alidrandco(a)yahoo.fr> > >> To: pharo-users(a)lists.pharo.org > >> Cc: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr>, farid arfi > >> <arfi_f(a)hotmail.com> > >> Bcc: > >> Date: Mon, 31 Jul 2017 01:38:58 +0200 > >> Subject: Threads safety in Pharo > >> Hi, > >> > >> Somebody once evoked the problem of threads safety in Pharo. With a friend > >> of mine who is expert in formal methods and process scheduling, we would > >> like to have a look on it. > >> Does anyone knows a good document describing the problem of Pharo with > >> threads safety or at least any document that we can start with? > >> > >> Thanks in advance, > >> Abdelghani > >> > >> > >> > > >

Aug. 11, 2017

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

by Stephane Ducasse

Tim I definitively think that we could turn it into a Pharo success story or something that we can keep on the web site because it is really nice. Stef On Thu, Aug 10, 2017 at 3:47 PM, Tim Mackinnon <tim(a)testit.works> wrote: > I just wanted to thank everyone for their help in getting my pet project > further along, so that now I can announce that PharoLambda is now working > with the V7 minimal image and also supports post mortem debugging by saving > a zipped fuel context onto S3. > > This latter item is particularly satisfying as at a recent serverless > conference (JeffConf) there was a panel where poor development tools on > serverless platforms was highlighted as a real problem. > > In our community weâve had these kinds of tools at our fingertips for ages - > but I donât think the wider development community has really noticed. > Debugging something short lived like a Lambda execution is quite startling, > as the current answer is âadd more loggingâ, and we all know that sucks. To > this end, Iâve created a little screencast showing this in action - and it > was pretty cool because it was a real example I encountered when I got > everything working and was trying my test application out. > > Iâve also put a bit of work into tuning the excellent GitLab CI tools, so > that I can cache many of the artefacts used between different build runs > (this might also be of interest to others using CI systems). > > The Gitlab project is on: https://gitlab.com/macta/PharoLambda > And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E > > Tim > > > On 15 Jul 2017, at 00:39, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - Iâve been playing around with getting Pharo to run well on AWS Lambda. > Itâs early days, but I though it might be interesting to share what Iâve > learned so far. > > Usage examples and code at https://gitlab.com/macta/PharoLambda > > With help from many of the folks here, Iâve been able to get a simple > example to run in 500ms-1200ms with a minimal Pharo 6 image. You can easily > try it out yourself. This seems slightly better than what the GoLang folks > have been able to do. > > Tim > >

Aug. 10, 2017

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

by Mariano Martinez Peck

Yeah, very nice. I just watched it all and looks cool. I am happy that the debugger/stack/context serialization is still breaking other people's mind :) There are a few limitations and problems with the serialization of debugger and materialization in another image. I think I listed those several times in the mailing list, but if you want, let me know, and I can remind them again (there we workarounds or help with the limits). Cheers, On Thu, Aug 10, 2017 at 5:57 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Impressive stuff!! > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Aug 10, 2017, at 9:47 AM, Tim Mackinnon <tim(a)testit.works> wrote: > > I just wanted to thank everyone for their help in getting my pet project > further along, so that now I can announce that PharoLambda is now working > with the V7 minimal image and also supports post mortem debugging by saving > a zipped fuel context onto S3. > > This latter item is particularly satisfying as at a recent serverless > conference (JeffConf) there was a panel where poor development tools on > serverless platforms was highlighted as a real problem. > > In our community weâve had these kinds of tools at our fingertips for ages > - but I donât think the wider development community has really noticed. > Debugging something short lived like a Lambda execution is quite startling, > as the current answer is âadd more loggingâ, and we all know that sucks. To > this end, Iâve created a little screencast showing this in action - and it > was pretty cool because it was a real example I encountered when I got > everything working and was trying my test application out. > > Iâve also put a bit of work into tuning the excellent GitLab CI tools, so > that I can cache many of the artefacts used between different build runs > (this might also be of interest to others using CI systems). > > The Gitlab project is on: https://gitlab.com/macta/PharoLambda > And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E > > Tim > > > On 15 Jul 2017, at 00:39, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - Iâve been playing around with getting Pharo to run well on AWS > Lambda. Itâs early days, but I though it might be interesting to share what > Iâve learned so far. > > Usage examples and code at https://gitlab.com/macta/PharoLambda > > With help from many of the folks here, Iâve been able to get a simple > example to run in 500ms-1200ms with a minimal Pharo 6 image. You can easily > try it out yourself. This seems slightly better than what the GoLang folks > have been able to do. > > Tim > > > > -- Mariano http://marianopeck.wordpress.com

Aug. 10, 2017

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

by Alexandre Bergel

Impressive stuff!! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Aug 10, 2017, at 9:47 AM, Tim Mackinnon <tim(a)testit.works> wrote: > > I just wanted to thank everyone for their help in getting my pet project further along, so that now I can announce that PharoLambda is now working with the V7 minimal image and also supports post mortem debugging by saving a zipped fuel context onto S3. > > This latter item is particularly satisfying as at a recent serverless conference (JeffConf) there was a panel where poor development tools on serverless platforms was highlighted as a real problem. > > In our community weâve had these kinds of tools at our fingertips for ages - but I donât think the wider development community has really noticed. Debugging something short lived like a Lambda execution is quite startling, as the current answer is âadd more loggingâ, and we all know that sucks. To this end, Iâve created a little screencast showing this in action - and it was pretty cool because it was a real example I encountered when I got everything working and was trying my test application out. > > Iâve also put a bit of work into tuning the excellent GitLab CI tools, so that I can cache many of the artefacts used between different build runs (this might also be of interest to others using CI systems). > > The Gitlab project is on: https://gitlab.com/macta/PharoLambda <https://gitlab.com/macta/PharoLambda> > And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E <https://www.youtube.com/watch?v=bNNCT1hLA3E> > > Tim > > >> On 15 Jul 2017, at 00:39, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> Hi - Iâve been playing around with getting Pharo to run well on AWS Lambda. Itâs early days, but I though it might be interesting to share what Iâve learned so far. >> >> Usage examples and code at https://gitlab.com/macta/PharoLambda <https://gitlab.com/macta/PharoLambda> >> >> With help from many of the folks here, Iâve been able to get a simple example to run in 500ms-1200ms with a minimal Pharo 6 image. You can easily try it out yourself. This seems slightly better than what the GoLang folks have been able to do. >> >> Tim >

Aug. 10, 2017

Re: [Pharo-users] [ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

by Esteban A. Maringolo

Hi Tim, Impressive pet project you have. And what a way to deliver! Not only with fun features never built before, but also with a documented repo and a detailed screencast. Congratulations. In my self interest, and indirectly for the Pharo community, I look forward to see more contributions like this from you. Regards! Esteban A. Maringolo 2017-08-10 10:47 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: > I just wanted to thank everyone for their help in getting my pet project > further along, so that now I can announce that PharoLambda is now working > with the V7 minimal image and also supports post mortem debugging by saving > a zipped fuel context onto S3. > > This latter item is particularly satisfying as at a recent serverless > conference (JeffConf) there was a panel where poor development tools on > serverless platforms was highlighted as a real problem. > > In our community weâve had these kinds of tools at our fingertips for ages - > but I donât think the wider development community has really noticed. > Debugging something short lived like a Lambda execution is quite startling, > as the current answer is âadd more loggingâ, and we all know that sucks. To > this end, Iâve created a little screencast showing this in action - and it > was pretty cool because it was a real example I encountered when I got > everything working and was trying my test application out. > > Iâve also put a bit of work into tuning the excellent GitLab CI tools, so > that I can cache many of the artefacts used between different build runs > (this might also be of interest to others using CI systems). > > The Gitlab project is on: https://gitlab.com/macta/PharoLambda > And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E > > Tim > > > On 15 Jul 2017, at 00:39, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - Iâve been playing around with getting Pharo to run well on AWS Lambda. > Itâs early days, but I though it might be interesting to share what Iâve > learned so far. > > Usage examples and code at https://gitlab.com/macta/PharoLambda > > With help from many of the folks here, Iâve been able to get a simple > example to run in 500ms-1200ms with a minimal Pharo 6 image. You can easily > try it out yourself. This seems slightly better than what the GoLang folks > have been able to do. > > Tim > >

Aug. 10, 2017

[ANN] PharoLambda 1.5 - Pharo running on AWS Lambda now with saved Debug sessions via S3

by Tim Mackinnon

I just wanted to thank everyone for their help in getting my pet project further along, so that now I can announce that PharoLambda is now working with the V7 minimal image and also supports post mortem debugging by saving a zipped fuel context onto S3. This latter item is particularly satisfying as at a recent serverless conference (JeffConf) there was a panel where poor development tools on serverless platforms was highlighted as a real problem. In our community weâve had these kinds of tools at our fingertips for ages - but I donât think the wider development community has really noticed. Debugging something short lived like a Lambda execution is quite startling, as the current answer is âadd more loggingâ, and we all know that sucks. To this end, Iâve created a little screencast showing this in action - and it was pretty cool because it was a real example I encountered when I got everything working and was trying my test application out. Iâve also put a bit of work into tuning the excellent GitLab CI tools, so that I can cache many of the artefacts used between different build runs (this might also be of interest to others using CI systems). The Gitlab project is on: https://gitlab.com/macta/PharoLambda <https://gitlab.com/macta/PharoLambda> And the screencast: https://www.youtube.com/watch?v=bNNCT1hLA3E <https://www.youtube.com/watch?v=bNNCT1hLA3E> Tim > On 15 Jul 2017, at 00:39, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - Iâve been playing around with getting Pharo to run well on AWS Lambda. Itâs early days, but I though it might be interesting to share what Iâve learned so far. > > Usage examples and code at https://gitlab.com/macta/PharoLambda <https://gitlab.com/macta/PharoLambda> > > With help from many of the folks here, Iâve been able to get a simple example to run in 500ms-1200ms with a minimal Pharo 6 image. You can easily try it out yourself. This seems slightly better than what the GoLang folks have been able to do. > > Tim

Aug. 10, 2017