sounds like following this strategy will have a deep influence in programming more functionally and use immutability a lot more.
> On Nov 14, 2014, at 12:31 PM, Sven Van Caekenberghe <[email protected]> wrote: > > >> On 14 Nov 2014, at 15:17, Esteban A. Maringolo <[email protected]> wrote: >> >> What are the benefits of running a Pharo server in the cloud on ARM >> architecture? > > Basically there are two server schools: the classic old school is only > interested in raw performance at any cost, a newer, alternative school thinks > that cheaper, massive parallel and more efficient (performance per watt) CPUs > can have advantages. This of course assumes the workload scales horizontally, > like in web applications and services. > > Here is the article where I learned about the Online Labs initiative: > > http://techcrunch.com/2014/11/13/online-labs-designed-its-own-arm-servers-to-take-on-aws-digitalocean/ > > http://armservers.com > >> Thank you! >> El Fri Nov 14 2014 at 11:14:02 AM, Sven Van Caekenberghe <[email protected]> >> escribió: >> Hi Andreas, >> >> I tried a precompiled VM, where are those instructions ? >> Are they relevant for ARM ? >> BTW, the problem on the Raspberry Pi was the glibc version (2.5 required). >> >> Sven >> >>> On 14 Nov 2014, at 14:52, Andreas Wacknitz <[email protected]> wrote: >>> >>> Am 14.11.14 um 12:00 schrieb Sven Van Caekenberghe: >>>> pthread_setschedparam failed: Operation not permitted >>> Did you follow the instructions from the readme file to allow for increased >>> thread priorities? >>> The heartbeat thread needs to run at a higher priority than the working >>> thread. >>> In Solaris I have to add priocntl privileges to users for this, where Linux >>> seem to have another way >>> described in the readme... >>> >>> Regards, >>> Andreas >> >> > >
