Magma July 2006

magma@lists.squeakfoundation.org

4 participants
5 discussions

queries update
by Chris Muller 01 Aug '06

01 Aug '06

Made some good progress on the queries this weekend. Adventurers willing to risk bugs may download individual packages dated since June 1st on SqueakSource, here is that list: Ma Armored Code-cmm.105 Ma base additions-cmm.65 Ma object serialization-cmm.150 Ma special collections-cmm.65 Magma client-cmm.207 Magma server-cmm.172 Things are really starting to look good, but I still need to do some more testing, thanks for your patience and understanding. Should you happen to download the individual packages, please let me know if you find any problems. - Chris

2 2

Tiny fix
by goran＠krampe.se 31 Jul '06

31 Jul '06

Hi Chris and all! When bulk loading 40000 objects I discovered this small bug - the fix is the inserted line "self resetLastClean" below. Obviously if we decide to clean after 30 seconds - then we need to reset lastClean. Otherwise it will start cleaning like a mad man after 30 seconds, which I of course experienced. :) Hmmm, I just noticed Chris has discovered this already. We have also experienced another problem on and off - but I haven't pin pointed it yet and it only appears when meddling around in development (halts and debuggers etc). The effect is that Squeak suddenly feel sluggish - and yes, behold - Magma is creating Processes like a machine gun. Running this snippet in fast sequence 5-10 times usually cleans them up enough to get it to stop: (Process allInstances select: [:p | p isSuspended]) do: [:pp | pp terminate; install: nil] It appears to be some issue in the proxy stuff. If noone else has seen it I can try to find the suspect method. regards, Göran shouldRemoveGarbageCollectedEntries | count size | Time millisecondClockValue - lastClean > 30000 ifFalse: [ ^ false ]. self resetLastClean. size := count := 0. objects keysAndValuesDo: [ : eachOid : eachObject | size := size + 1. eachObject ifNotNil: [ count := count + 1 ] ]. ^ size > (count * 2)

2 1

MagmaServerLoader-cmm.17
by Chris Muller 31 Jul '06

31 Jul '06

While working on the queries I noticed a couple of bugs worth applying to the current stable version (without queries), even though I think the queries version is right around the corner. Keith Hodges submitted a great fix to allow relative path specification, thanks Keith! A performance improvement attempted twice before is now finally realized, by minimizing the impact of shouldRemoveGarbageCollectedEntries. Sheesh, under certain circumstances we have been enduring some real pain, please feel free to speak up you guys so we can get these kinds of things knocked out! These fixes will be in the upcoming queries version, of course. - Chris

1 0

Magma Seaside Integration
by Martin Schubert 08 Jul '06

08 Jul '06

hey out there, does anybody know to which version of seaside (i am using the 2.6b1 branch and i get WARenderCanvas failure after following the configure link) the sushi store example : seasideSushiStoreWithMagma.cs.gz is working? best regards martin

2 2

Some questions
by Norberto Manzanos 06 Jul '06

06 Jul '06

Hi Chris and Magma people. Finally I am uploading the data from my old database to magma. I found some errors in my objects, but there were a critical question on the way you commit when using a large collection. If I perform a single commit for each element, it takes too much. With a commit for all the collection an error raises: 'couldnt serialize more than 10 megabytes'. So I had to use a mixed solution, a commit for x elements of the collection. I'm uploading about 150000 objects, and grouped by 500 and it worked fine. The question is: Is there a way to know how space will occupy each object on the serializer, so I can improve this groups of commits to consume the less possible time? Another question. I was wandering what would happen if I change the class definition of my objects when the objects are alive in the database. I'm making some test to get the answer but I want to know how Magma is expected to work if a) I add an instance variable, b) remove an instance variable, c) change the hierarchy of the class d) change the class of a collaborator, etc. An finally, we need the method #asOrderedCollection to transform a MagmaCollection. It's not implemented, Object definition is taken. I'm not sure whether magma uses this implementation (Object >> #asOrderedCollection). Can we implement this method as a collect in the normal way? Thanks in advance. Norberto Manzanos

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma July 2006