Hi vince

I���m often working in the alpha version and it is stable but from time to time I have some crashes. 
In headless mode and interaction you have processes that can lock the system or others and we got some GC memory corruption.  
This is why we will introduce TaskIt-Core in Pharo 90.

S


On 14 May 2020, at 00:21, Vince Refiti <vince.refiti@trapezegroup.com.au> wrote:

Hello Sven

This is the kind of thing I like to see. Gives me more confidence in recommending Pharo to management for production use.

Just some things that still concern me though: Why are people surprised at discovering that Pharo is capable of such uptimes? Are people experiencing instability with Pharo in production settings? If so, what kind of instability are people experiencing?

Thanks, Vince

-----Original Message-----
From: Pharo-users <pharo-users-bounces@lists.pharo.org> On Behalf Of Sven Van Caekenberghe
Sent: Tuesday, 12 May 2020 6:06 PM
To: Pharo users <pharo-users@lists.pharo.org>
Subject: [Pharo-users] Uptime

EXTERNAL: Do not click links or open attachments if you do not recognize the sender.

Hi,

So here is a little anecdote from the real world. I was planning to update the OS on my Linux server, from Ubuntu 18.04 LTS to 20.04 LTS (Long Term Support). This small (Digital Ocean, 1GB RAM, 1 Core) cloud server runs 3 Pharo images with public facing web sites.

The machine itself reports:

$ uptime
12:37:50 up 530 days, 21:46,  1 user,  load average: 0.02, 0.04, 0.01

which means it hasn't been powered down or didn't restart in 530 days.

I was surprised to discover that 2 of the Pharo images on that machine did just as well:

$ ./repl.sh
Connecting to Telnet REPL at locahost:41011 Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Neo Console Pharo-7.0+alpha.build.660.sha.2eb9bd2f41e7b0bd8f9f4190906910f83c178ab1 (32 Bit)
pharo> get system.uptime
405 days 20 hours 29 minutes
pharo> quit
Bye!

$ ./repl.sh
Connecting to Telnet REPL at locahost:41001 Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Neo Console Pharo4.0 of 18 March 2013 update 40620
get system.uptime
530 days 21 hours 44 minutes
quit
Bye!

So both Pharo 7 and Pharo 4 kept on doing their jobs for a very long time. I think this is a testament to the stability of Pharo and to what is possible.

Regards,

Sven

--
Sven Van Caekenberghe
Proudly supporting Pharo
https://urldefense.com/v3/__http://pharo.org__;!!I_DbfM1H!U29_nUf8k6rmGjsp2AQSL8IDqW4-0JavFUItRuu0N2MQbNF35jnzLuQJwzgetkVf2_QA6g64JQ$
https://urldefense.com/v3/__http://association.pharo.org__;!!I_DbfM1H!U29_nUf8k6rmGjsp2AQSL8IDqW4-0JavFUItRuu0N2MQbNF35jnzLuQJwzgetkVf2_TO4j9SBA$
https://urldefense.com/v3/__http://consortium.pharo.org__;!!I_DbfM1H!U29_nUf8k6rmGjsp2AQSL8IDqW4-0JavFUItRuu0N2MQbNF35jnzLuQJwzgetkVf2_RhpurXTg$

--------------------------------------------
St��phane Ducasse
03 59 35 87 52
Assistant: Julie Jonas 
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley, 
Parc Scientifique de la Haute Borne, B��t.A, Park Plaza
Villeneuve d'Ascq 59650
France