Magma August 2009

magma@lists.squeakfoundation.org

14 participants
17 discussions

start up and shutdown.
by Ramiro Diaz Trepat 31 Aug '09

31 Aug '09

Hi guys, I want my application to automatically create a repository with some basic date if my image is started somewhere that does not have a preexisting database. I was making a few tests, basically to see what happened with Magma if when restarting an image that had an open session, the database directory was not found. I opened my session with something like this. magmaServer := MagmaServerConsole new. [ magmaServer open: path ] on: Error do: [ :ex | Transcript show: ex ]. magmaServer processOn: 51001. magmaServer shutdown. I realized then that in spite of runnring the last #shutdown, if I closed the image and then restarted it it was still reopening the repository. Then I executed things like: MagmaRepositoryController initialize. MagmaSession cleanUp. magmaServer controller closeRepository. Neither could avoid the automatic attempts to reopen the repository after I restarted the image. Then, I lost the pointer to that magmaServer and every time my image starts it still tries to open that repository and it fails. What are the commands to execute to reset it all? to stop Magma from trying to open anything at all at start up so I can start from a clean slate again. Thanks r.

2 2

can magma now run 24x7?
by merlyn＠stonehenge.com 30 Aug '09

30 Aug '09

For SmalltalkSolutions in 2008, I put Magma in the "not ready for 24x7" category, simply because Magma had to be taken offline to vacuum the database from time to time. I'm presuming that with the new high-availability update, this requirement is now gone, but can someone confirm that for me? I have clients who need to know. :) -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion

2 1

Great News - Pharo Support - Now Seaside.
by Timothy James Ziebart 27 Aug '09

27 Aug '09

Hi All. Thank you Chris for Magma, I am planning on using it on a commercial website. I will publish a link when it is ready. Now for my challenge - Seaside support. The questions of course are open to all and comments are welcome. Thank you in advance. I've read all that I can on the subject but I still have a number of questions. I am running the latest Pharo with the latest Magma loaded. All packages were loaded via Monticello. 1. The state of Jetsam. I installed the latest but now am unable to configure a seaside app. On the configuration page the options are "fixed set by client". Any suggestions? My concern -- is this is indicative of other problems -- maybe related to Pharo? 2. Magma SeasideHelper - Given the question about Jetsam this is a non-starter. I would assume SeasideHelper is of no use without Jetsam. 3. Magma Seaside - http://wiki.squeak.org/squeak/5817 - Can I use the examples and implement Magma as indicated? I am currently using a custom WASession for my purposes and will most likely establish a Magma connection for each Seaside session. Local database for development - remote for production. 4. Are there other implementation options - sample code? I understand the Gjallar implementation is not recommended - true?

4 6

Magma industrial site
by Chris Muller 26 Aug '09

26 Aug '09

I am pleased to announce Magma R42 is now running in production at a tier-1 mobile carrier performing real-time, nationwide call control for a crucial location-aware voice and SMS application. Magma passed the operator's high-availability requirements and disaster-recovery fail-over test on the first attempt.

3 2

"Magma Performance" page updated
by Chris Muller 26 Aug '09

26 Aug '09

I just updated the benchmark results running R42, can be reviewed here: http://wiki.squeak.org/squeak/5606 These benchmarks represent the fastest a single-client can go under the following circumstances: - local connection (no serialization) - loopback connection (serialization, but no network latency) - 100Mbps LAN connection - 54Mbps wireless-G LAN connection This represents how fast a single-client can do various things, not how fast a single-server can go. A single-server can go much faster but that is a question of scale, not speed. These benchmarks are a measure of client speed only, not server scale. The "over-the-Internet" is not done yet. - Chris

1 0

Fwd: Why Gjallar is a "bad" Magma example (was Re: Great News - Pharo Support - Now Seaside.)
by Miguel Cobá 26 Aug '09

26 Aug '09

> > What version of Magma are you running? As for performance, Magma came > a long way in performance department in r41 and r42. If you still > have performance "problems" in r42 then I'm _really_ curious to see > the stats report from a troubled client session as well as the server. > If you: > > myMagmaSession statistics report > > for the client, or, you can alternatively print it to any stream (if, > for example the printString limit can sometimes be hit with these > reports): > > myMagmaSession statistics printReportTo: someStream > > and post it up here (or send me private e-mail if it's too sensitive) > it would reveal a lot about the _nature_ of Gjallers usage of Magma > and potential problem areas.. > > If you are running an HA (which provides more scale, but necessarily > more speed for individual clients), then please be sure to get stats > from _both_ the primary and secondary: > > myMagmaSession serverStatisticsPrimary report > > and > > myMagmaSession serverStatisticsSecondary report > I know that am a bit lazy in reading the code to learn the usage of a package. I always prefer tutorials and examples. Given the *huge* codebase of magma and the complexity, for a common guy like me, the laziness is bigger. But, when reading the magma mailing list I always found gems like this (that I have been collecting for future reference) that it appears that nobody else knows. This is the reason for my call for a better documentation for magma. It is really a very good piece of software and I'm sad that doesn't receive more acceptance and attention. We need to collect them and show the people how to use magma in everyday scenarios. Now that I will have more free time I will try to do a little tutorial about magma and I will include these code snippets for others to see and use. Cheers Miguel Cobá http://miguel.leugim.com.mx

2 1

MaClientProcess class/variable not found on method MagmaRepositoryController>>fullBackupTo:
by Miguel Enrique Cobá Martinez 25 Aug '09

25 Aug '09

Hi Chris, I'm trying to load magma from squeaksource.org/Magma with the code: Installer ss project: 'Magma'; install: '1.0r42 (server)'. When creating a repository with: MagmaRepositoryController create: '/home/miguel/pharo/magma/' root: Dictionary new. I got the following error: UndefinedObject(Object)>>doesNotUnderstand: #doBlock: [] in MagmaRepositoryController>>fullBackupTo: BlockClosure>>ensure ... and the method fullBackupTo: has a reference to MaClientProcess doBlock: that I can resolve to a class var or a class name. I have also loaded 1.0r42 (tester).mcm but I can't find the class anywhere in the image. Does a package is missing in the mcms? This was done on a update 10418 PharoCoreImage. Cheers -- Miguel Cobá http://miguel.leugim.com.mx

3 2

[Fwd: Re: Great News - Pharo Support - Now Seaside.]
by Miguel Enrique Cobá Martinez 22 Aug '09

22 Aug '09

-- Miguel Cobá http://miguel.leugim.com.mx

1 0

[ANN] Magma release 42
by Chris Muller 21 Aug '09

21 Aug '09

I am pleased to announce a new release of Magma. Release 42 brings unprecedented scale and availability of persistent domain models to Squeak users. In particular, a single logical repository can now be served from multiple servers simultaneously, each hosting their own physical copy. To maintain consistency, just one server receives writes and broacasts commit-records to "warm-backup" servers asynchronously. The warm-backups ensure to keep themselves constantly up to date automatically. Individual servers in the "Node", even the primary, can be brought off-line and back on-line without disruption to clients. Maintenance routines such as full-backup and compression may optionally be run while a repository is off-line, resulting in true 24x7 operation with no performance degradation due to maintenance jobs. The more physical copies of a repository that are brought on-line, the more read-scale the overall Node will provide. For more details, see: http://wiki.squeak.org/squeak/6101 Scales up as well as down: Magma retains it's existing ability to scale an existing, large, multi-user repository _down_ to a single user on a single laptop easily, without a single change to application code. This can be very useful for diagnosing production issues without disturbing production. 42 one-click loads cleanly into 3.9, 3.10 and Pharo, and is supported on those images. For now, the Magma home page still resides at: http://wiki.squeak.org/squeak/2665 - Chris

4 5

[ANN] Magma release 42
by Ramiro Diaz Trepat 21 Aug '09

21 Aug '09

Great ! Thanks for your work Chris ! Cheers r. 2009/8/20 Miguel Enrique Cobá Martinez <miguel.coba(a)gmail.com> El jue, 20-08-2009 a las 13:54 -0500, Chris Muller escribió: > > I am pleased to announce a new release of Magma. Release 42 brings > > unprecedented scale and availability of persistent domain models to > > Squeak users. In particular, a single logical repository can now be > > served from multiple servers simultaneously, each hosting their own > > physical copy. To maintain consistency, just one server receives > > writes and broacasts commit-records to "warm-backup" servers > > asynchronously. The warm-backups ensure to keep themselves constantly > > up to date automatically. > > > > Individual servers in the "Node", even the primary, can be brought > > off-line and back on-line without disruption to clients. Maintenance > > routines such as full-backup and compression may optionally be run > > while a repository is off-line, resulting in true 24x7 operation with > > no performance degradation due to maintenance jobs. The more physical > > copies of a repository that are brought on-line, the more read-scale > > the overall Node will provide. For more details, see: > > > > http://wiki.squeak.org/squeak/6101 > > > > Scales up as well as down: Magma retains it's existing ability to > > scale an existing, large, multi-user repository _down_ to a single > > user on a single laptop easily, without a single change to application > > code. This can be very useful for diagnosing production issues > > without disturbing production. > > > > 42 one-click loads cleanly into 3.9, 3.10 and Pharo, and is supported > > on those images. > > > > Pharo! > > I have to say thank you very much Chris, for the effort that you and > Stuart have done. I am surprised that the release 42 already has support > for Pharo, I thought we would have to wait for the next version. > > In this moment am downloading it and testing my app with it. > > What a great news! > > Cheers > > > For now, the Magma home page still resides at: > > > > http://wiki.squeak.org/squeak/2665 > > > > - Chris > > _______________________________________________ > > Magma mailing list > > Magma(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/mailman/listinfo/magma > -- > Miguel Cobá > http://miguel.leugim.com.mx > > _______________________________________________ > Magma mailing list > Magma(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/magma >

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma August 2009