Magma

magma@lists.squeakfoundation.org

722 discussions

Fwd: Memory problem
by Igor Stasenko 11 Oct '10

11 Oct '10

On 11 October 2010 13:46, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hello. > > I run some test in pharo1.1 and magma installed from configuration. I insert > 100000 objects to local Magma db. > I use MargaCollection for this. > > And after test I have grow memory size. Before I have 90 mb. After I have > 140 mb. > > My code for test is: > > session commit: [entitiesGroup entities add: payment]. > session stubOut: entitiesGroup. > session finalizeOids. > Smalltalk garbageCollect > > entitiesGroup entities is MagmaCollection. > > During test I see that "payment class allInstances size" don't changed. Its > ok. I do stub/finalize stuff for this. > But memory usage grow. Its bad. > > At the end of test I watch in MaWeakValueDictionary allInstances. And I > found that some instance has 141000 items. And 140000 items is nil. > (self select: [:each | each isNil] a MaWeakValueDictionary(size 140064)). > > This is my problem > What I do wrong? > > If i remember correctly, there are a mechanism, which should clean it up periodically. But not too often , to prevent too much processing. > > > > > _______________________________________________ > Magma mailing list > Magma(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/magma > > -- Best regards, Igor Stasenko AKA sig.

2 1

CommitSafelly
by Denis Kudriashov 05 Oct '10

05 Oct '10

Hello, I attach method commitSafelly: aBlock for session. It's garanties that when commit block will failed transaction will aborted. Maybe some analogue already exists?

2 1

possible bug
by Elliot Finley 01 Oct '10

01 Oct '10

Hello, I just started playing with Magma, so it may be just me not knowing how to use it. I have a server running in image A on my machine. In image B on the same machine I have the following in a workspace: mySession := (MagmaRemoteLocation host: '10.215.90.59' port: 51001) newSession. mySession connectAs: 'elliot'. myRoot := mySession root. If I use '127.0.0.1' or 'localhost' as the host, then I get a timeout error when calling mySession>>connectAs: It says 'ConnectionTimedOut: Cannot connect to 10.215.90.74:51001' (10.215.90.74 is an address that I've had at one time). If I specifically use '10.215.90.59' as the host, then connectAs: works as normal, but then the following statement 'myRoot := mySession root.' fails with the 'ConnectionTimedOut: Cannot connect to 10.215.90.74:51001' error. Has anyone seen this before? What am I doing wrong? Thanks in advance, Elliot

2 2

possible bug
by Elliot Finley 28 Sep '10

28 Sep '10

I forgot to mention my machine and version of Magma. Macbook Pro (Max OS X 10.6) Pharo-1.1-11411dev10.07.1 Magma 11r2 Thanks, Elliot

1 0

magma collections - indexing and searching.
by Timothy James Ziebart 18 Sep '10

18 Sep '10

Hi all, I have setup a MagmaCollection with two indexes. I loaded the initial data and it appeared to be successful. I have the following search: getMessagesFor: aModule fieldName: aFieldName "Retreive message from the database" |aReader| aReader := (self root at: #fields) where:[ :each | (each fieldName at: aFieldName ) & (each moduleName at: aModule)]. ^aReader asArray. For the records loaded initially this works fine. However any records I add in the application do not get retrieved using the above method. But I can recover the new records searching on the fieldName and moduleName separately. So the indexes appear to be correct. Any Suggestions? Am I missing a step? Below I've included more details on the initial setup. Thanks again for your help. Tim Initial Setup: myCollection := MagmaCollection new. newIndex := MaSearchStringIndex attribute: #fieldName. myCollection addIndex: newIndex. newIndex := MaSearchStringIndex attribute: #moduleName. myCollection addIndex: newIndex. I added my records using a do loop: (fields ) do:[ :each | myCollection add: each ]. The resulting collection was written to Magma. LBCRepository commit:[LBCRepository root at: #fields put: myCollection ]. The addField method in the application is as follows: LBCRepository class method>> addField: aField self commit:[(self root at: #fields) add: aField]

2 1

Loading latest client and server.
by Timothy James Ziebart 05 Sep '10

05 Sep '10

I managed to install the magma server on a pharo 1.1 image including the OBMagmaBrowser. It appears to work fine. I can browse the repository. In a second image I loaded the client. When I run session := (MagmaRemoteLocation host: 'server' port: 51969) newSession. It appears to work properly give me an instance of a Magma Session. But when I go to connectAs: 'user' on the session I get the following message: MagmaReadServerTooFarBehind: MaSaveAndExitImageRequest cannot have variable sized instances Any Ideas? I tried using MagmaSession host: port: and I get the same result. Thank you. Tim

2 1

[ANN] Magma 1.1r2
by Chris Muller 31 Jul '10

31 Jul '10

I am pleased to announce a new release of Magma containing my updates since 1.1r1: - All underscore assignments have now been updated to ANSI assignments. - When opening the server, a file called "_open" is created in the repository directory, to indicate the repository is open. The file is deleted when the repository is closed gracefully. This is intended to help protect from accidentally letting two OS processes open the same repository files. - Resurrected MagmaDictionary! It is just like a Dictionary except that it inherits the properties of Magma's LargeCollections, such as size and concurrency. - Added Collection>>#asMagmaArray and MagmaArray>>#add:. - Added check for an additional way to run Squeak in headless mode: the "-vm-display-null" option. - Added MagmaSessionRequest class>>#signalNewReadStrategy: so that domains may signal new ReadStrategies to any listening sessions. - Added MagmaLocalLocation>>#findSession, a convenient counterpart to #newSession that first checks there is already a session open on that location and, if so, use that one. Otherwise, create and answer a new one. - Support for persistent, simple BlockClosures (e.g., with only references to arguments, not "self", any instVars or globals). - Choose automatically between an appropriate MaDictionary subclass, depending on whether the new Weak-Finalization mechanism from Igor is supported. - Several other minor fixes. The following represent the 1.1r2 configuration, in load-dependent order: "Magma client" { 'Collections-BTree-lr.73.mcz'. 'Ma exception handling-cmm.36.mcz'. 'Ma base additions-cmm.174.mcz'. 'MaFixedWidthReport-cmm.7.mcz'. 'Ma Statistics-cmm.24.mcz'. 'Ma files additions-cmm.13.mcz'. 'Ma contextual search-cmm.34.mcz'. 'Ma special collections-cmm.114.mcz'. 'WriteBarrier-cmm.28.mcz'. 'Ma Squeak domain-cmm.34.mcz'. 'Ma proxy support-cmm.42.mcz'. 'Ma traverse object graphs-cmm.31.mcz'. 'Ma object serialization-cmm.234.mcz'. 'Ma client server-cmm.215.mcz'. 'Magma client-cmm.490.mcz' } "for Magma server add" , {'Magma server-cmm.406.mcz'. } "for Magma tester add" , { 'Ma Armored Code-cmm.148.mcz'. 'Ma special collections tester-cmm.14.mcz'. 'Ma object serialization tester-cmm.32.mcz'. 'Magma tester-cmm.367.mcz' } These package versions are available in the "MagmaTester" project of squeaksource.com. - Chris

4 8

[ANN] ConfigurationOfMagma for Magma 1.1r1
by Miguel Enrique Cobá Martínez 20 Jul '10

20 Jul '10

I'm pleased to announce that the ConfigurationOfMagma now includes support for loading version 1.1r1 of Magma. In a Pharo or PharoCore 1.0 image evaluate: Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. To install the Magma Client evaluate: ConfigurationOfMagma project latestVersion load: 'Client' To install the Magma Server evaluate: ConfigurationOfMagma project latestVersion load: 'Server' To install the Magma Tester evaluate: ConfigurationOfMagma project latestVersion load: 'Tester' Then if you want, run the test suite. Evaluate in a workspace: MagmaTestCase allowWriteBarrier: false. MagmaTestCase fullSuite maDebug. Enjoy -- Miguel Cobá http://miguel.leugim.com.mx

2 4

ConnectionTimedOut: Cannot connect to 127.0.1.1:53604
by Germán Arduino 11 Jul '10

11 Jul '10

I installed the latest version of Magma, on a Squeak 4.1 image, following the Installer script published on the swiki. After installation I defined a new repository pointing to a simple model (singleton) I've here. Then, I started a console to start playing with. But, anytime that I try to save the image, of start this image I get the error of the subject. What means? Why is talking of a port I not used? (I only started the console on port 51001 as usual). I tried shuting down the console, and other things, but this connection time out is allways here. Thanks. -- ================================================= Germán S. Arduino <gsa @ arsol.net> Twitter: garduino Arduino Software & Web Hosting http://www.arduinosoftware.com PasswordsPro http://www.passwordspro.com =================================================

1 0

Maui video?
by Chris Muller 14 Jun '10

14 Jun '10

> Or maybe I'll just load up the DB with my domain in a Squeak image where all > of these tools work :). I've watched a video of Maui in action and its > pretty cool! What video?!

2 1

← Newer
1
...
10
11
12
13
14
15
16
...
73
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma