Magma

magma@lists.squeakfoundation.org

722 discussions

Updating a 'live' environment
by Amir Ansari 17 Nov '10

17 Nov '10

What is the best practise for updating a 'live' environment? More specifically: suppose I have a database that is accessed by several instances of an application (say, a load-balanced Seaside app), but need to change the objects comprising the database in any of the following ways: (1) Add/remove instance variables to/from a class that is persisted in a MagmaCollection; (2) Add/remove indexes to/from a particular MagmaCollection (perhaps after the changes in (1)); (3) Re-factor some of the classes, thus making minor changes to the schema ... how could the database be updated? Is there also some way to update all the existing objects in the database to reflect the new changes? Amir

2 2

Magma collection - where:
by Facundo Vozzi 16 Nov '10

16 Nov '10

Hi, I've this code: - self customers select: [:aCustomer | aCustomer name asUppercase beginsWith: firstsLetterOfName asUppercase] It works ok and with good perfomance but "customers" is a magma collection so I would like use where: because the collection has a index on #name attribute. - self customers where: [:each | aCustomer name = firstsLetterOfName asUppercase] It works but I had two problems, the first one is that the meaningfulCharacters of MaSearchStringIndex is 5 and then it works if I write exactly the 5 firsts letter of the name. The second problem is that I can't send asUppercase beacuse name is a MaClause. So, my question is: Can I use where: for this funcionality or I need use select:? If you think that where: is appropiate, Do I need create a new king of index to reach that? Thank you, Facu p.s.: I'm using the first code in the method of customersOfNameBeginsWith: selector and i used it on a autocompletation jquery input control.

3 5

Magma, Seaside and Magrite integration
by Facundo Vozzi 15 Nov '10

15 Nov '10

Hi all, I added magma session to my application seaside session (a subclass of WASession) so each user has his own magma session. My problem is with magritte description because I need, on the class side, set list of options. By example: User class >>descriptionRol "Answer a magritte meta description for the receiver rol attribute." ^MAMultipleOptionDescription new accessor: #roles; label: 'Roles'; priority: 200; componentClass: MAListCompositonComponent; options: MySystem singleton roles; beSorted; yourself The problem is "MySystem singleton roles" beacuse is in other magma session when the user add or edit an instance of User on the seaside application. I "hack" my seaside components to override the options with a collection of instances (by example: Rol allInSession: aUserSession) inside of the user session but it's very ugly. Just a test. How do you configure the maggrite description to deal with this problem? Is a common practice add a new magma session in every session session? Thanks in advance, Facu

3 3

[ANN] Magma 1.2 alpha1
by Chris Muller 14 Nov '10

14 Nov '10

I have posted a new configuration of the latest Magma version. It is in the "MagmaTester" project of squeaksource, under 1.2alpha1. If you are doing Magma development, please use this version as there have been many performance improvements over the current "stable" version. For Pharo users, please load the attached WeakOrderedCollection, which Magma needs. This has been integrated into the Squeak trunk and I hope Pharo will do the same (just 3 new methods). I have been too busy to test Magma on the latest Pharo so let me know if the test suite doesn't pass. I'd like to reiterate that I support for Magma on this list. There have been cases of folks using Magma incorrectly and then drawing questionable conclusions before ever asking on this list. - Chris

3 5

Magma is the right choice?
by Facundo Vozzi 12 Nov '10

12 Nov '10

Hi Chris, list, I'm using magma for an application that I'm making (for fun) since 3 months ago. It's a web based (pharo + seaside) query system. All is fine with magma and my model is going to be very object oriented and very clear. I'm happy of using magma but my uncertainty it's about scaling and performance issues because It will start with 20000 customers and 100 transactions/year for each one. The system is mainly for query of the commercial situation of each client. ¿You think that magma is suitable for this type of application? Sorry my poor english. Thanks in advance, Facundo ps: i'll test it with masive data input and query but it's important for me your opinion.

2 2

About Magma performance
by Chris Muller 12 Nov '10

12 Nov '10

There has been a lot of discussion about Magma performance recently, and so I would like to try to address this question about performance. The new 1.2 alpha just announced addresses two major performance bottlenecks; the finalization process and the slowness of become:. There are many improvements since 1.1; please use 1.2 releases for all new development. Note: 1.1 repositories require an upgrade to be read with 1.2. I don't know of any tool or framework for Squeak or Pharo that comes close to offering the number and level of performance measuring and tuning tools as Magma. MagmaBenchmarker is the place to start. It's available in the "Magma Tools" package. The numbers reported by the benchmarker are best-case, so it's a good litmus test of whether to consider Magma for the job. There are also a bunch of statistics Magma captures while running. Statistics are captured by each client-session, and the server tallies its own statistics too. I did this for Hilaire a couple of years ago to improve Magma's performance over low-latency networks (ISDN); by compressing the data sent over sockets. This statistics-gathering enhancement is designed so that Magma users can simply print the report, paste it here on this list, and reveal a lot about how your application uses Magma. Of course, MessageTally spies are always very useful too. All of these diagnostic tools are useful in determining which performance tuning tools should be employed for improvement. I would like to encourage use of these tools and, when all else fails, post a question here. If you can't include a change-set that replicates a problem, then background information with a Message spy will be helpful. - Chris

4 4

Magma & Multiple Cores
by Udo Schneider 25 Oct '10

25 Oct '10

All, I'm currently thinking about how to scale a Magma based Seaside Application efficiently. As the majority of requests are read-only the idea of using Magma HA came to my mind ... thus a few points I'm not quite sure about. Multiple Magma Servers on one physical server: As Squeak/Pharo is not SMP-capable I was thinking of running one server image per physical CPU core on the DB Server. One of those images would host the primary while all other images would host read-only secondaries. As the requests are primarily read-only this should give (in theory) a more or less linear increase (with cores) in read performance ... or did I miss something? Local secondary server on Web frontend server: Given that the intended webserver machines are quad core I was thinking of running three seaside images + one secondary magma image on them. The idea is that a local read-only replica should be much faster to query than over the network. However I'm not even sure if it is possible for a MagmaClient to configure preferred servers. My current thinking is start a remote MagmaSession against the locally running (secondary) Magma server image. My understanding is that all read requests are handled by this server then - only write requests will be sent to the primary. Am I making things much too complicated? Best Regards, Udo

2 1

Looking for real-world Magma application
by Igor Stasenko 21 Oct '10

21 Oct '10

Hello all, sorry for cross-posting. :) I'd like to ask you, if anyone could share either an image or installation with application, which using Magma OODB. I'd like to use it & test how changing different aspects of Magma internals could affect the performance. There's many tricks, which is known by Chris how to speed it up by cleverly fine-tuning various Magma options, like read strategy etc. But what i'd like is to see, is some setup, used by people, and by taking it, see how it could make run faster, without changing an application code. I remember, someone gave a talk @ ESUG, that they were using Magma for their application, but then forced to switch to another DB layer, because they had bad performance issues. It would be good, if you could give me the code, so i can run it and see if things could be improved. Its not a problem, if code is not open-source, we could sign an NDA, if this is necessary. I need something real, simply because benchmarks sometimes not representative. :) -- Best regards, Igor Stasenko AKA sig.

1 0

Range Queries fail for MaSearchStringIndex when using Umlauts
by Udo Schneider 15 Oct '10

15 Oct '10

All, I'm currently using Magma to perform a prefix search on City names. I found out that this fails if the string contains umlauts or, to be more precise, if the last given char is not Ascii. E.g. myCollection where: [ :reader | reader read: #city from: 'Me' to: 'Me' maAlphabeticalNext] works fine. Changing the prefix to 'Mü' fails (no result). I assume that this is somehow connected to a) maAlphabeticalNext and b) the "allowed" characters for MaSearchStringIndex (BTW: #beAscii doesn't help here). I'm currently using MaByteSequenceIndex to circumvent the problem but I am not sure whether this is the intention. I attached a Testcase which shows the problem. Thanks, Udo

2 2

Memory problem
by Denis Kudriashov 13 Oct '10

13 Oct '10

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?

2 1

← Newer
1
...
9
10
11
12
13
14
15
...
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