<div>Now I'm getting a performance problem.</div><div><br></div><div>I'm bulk loading transactions in sets (from a file) of 1250. Each of one has references to 3 objects, 3 numbers and 2 dates.</div><div><br></div>
<div>When I test it without setting the customer it take to me 614 milliseconds to create the 1250 instances but if I look up for each client according to the client code it take to me 204158 milliseconds (3.40 minutes). </div>
<div>Customers is a MagmaCollection and this is the method of the message that I'm sending 1250 times:</div><div><br></div><div><div>customerAtDocumentNumber: unString sex: otroString</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>"Devuelve un invividuo o una organizacion dependiendo de si unString corresponde a un número de documento o a un número de cuit. NOTA: se debe tener en cuenta el sexo por existir números de dni repetidos entre varones y mujeres."</div>
<div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>| aFewCustomers |</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>aFewCustomers := self customers where: [ :each | (each documentNumber = unString)].</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>^customers detect: [:each | each documentNumber = unString and: [each sex = otroString]] ifNone: []</div><div><br></div><div><br></div><div><br></div><div>
Customers has an index on documentNumber. Now I go to profile it but I need to find how to do it in Pharo. </div><div>I thing that I can switch customers from MagmaCollection to MagmaDictionary and set the document number + sex how the key. What do you think?</div>
<div><br></div><div>See you,</div><div>Facu</div><div><br></div><br><div class="gmail_quote">On Thu, Dec 9, 2010 at 7:36 PM, Facundo Vozzi <span dir="ltr"><<a href="mailto:facundov79@gmail.com">facundov79@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
<br>
</div>If you do a copy, then you will be creating multiple instances of<br>
various "system entities", which I'm guessing don't want to do; you<br>
would rather have just one instance, referenced from multiple<br>
transactions, right?<br></blockquote><div><br></div></div><div>Yes, you're right I don't want multiple instances. </div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
So all you need to do is just look-up the *equivalent* Code in session<br>
which is doing the loading. It will be the one identical instance in<br>
the repository.<br></blockquote><div><br></div></div><div><div>Yes, to do that I'm passing the session which is doing the loading by </div><div>argument. But I think that my error here is that I'm implementing the protocol to get one entitiy instance by code or name on the Entity class side. I think is </div>
<div>better implement it, by example #clientOfCode: aCode, in my system instance</div><div>which is the root of each session. In this manner I don't need pass the user session by argument. I think that my traditional database mapping thinking betrayed me</div>
</div><div class="im"><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
But yes, this is one of the use-cases for which FP's were invented, it<br>
can be a more elegant solution, especially if the number of Codes is<br>
always changing or increasing. See<br>
MagmaTestCase>>#testForwardingProxy.<br></blockquote><div><br></div></div><div>Yes, I will see it right now.</div><div><br></div><div>Facu</div><div><div></div><div class="h5"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<font color="#888888"><br>
- Chris<br>
</font><div><div></div><div><br>
<br>
> Thanks for your help,<br>
> Facu<br>
><br>
> On Thu, Dec 9, 2010 at 4:35 PM, Chris Muller <<a href="mailto:asqueaker@gmail.com" target="_blank">asqueaker@gmail.com</a>> wrote:<br>
>><br>
>> I'm not sure I fully understand the context, but a third option might<br>
>> be to use ForwardingProxies. Especially if the shared objects can be<br>
>> updated by only one session (like a batch updater, for example). Then<br>
>> every other (user client) session will share the same instances in<br>
>> memory.<br>
>><br>
>> HTH,<br>
>> Chris<br>
>><br>
>> On Wed, Dec 8, 2010 at 1:13 PM, Facundo Vozzi <<a href="mailto:facundov79@gmail.com" target="_blank">facundov79@gmail.com</a>><br>
>> wrote:<br>
>> > Hi all,<br>
>> > I'm refactoring my code and I found that I have two ways to do the same<br>
>> > in<br>
>> > distint parts of my system.<br>
>> > 1) Entity class >> atCode: aCode<br>
>> > "Answer the receiver instance with code equal to aCode or evaluate<br>
>> > aBlock if<br>
>> > it doesn't exists."<br>
>> > ^(self all detect: [:one | one code = aCode]) copy<br>
>> > or<br>
>> > 2) Entity class>> atCode: aCode inSession: anUserSession<br>
>> > "Answer the receiver instance with code equal to aCode or evaluate<br>
>> > aBlock if<br>
>> > it doesn't exists."<br>
>> ><br>
>> > ^(self allInSession: anUserSession) detect: [:one | one code =<br>
>> > aCode]<br>
>> > The difference is that 1 is using the shared session so I need copy the<br>
>> > object to be used (referenced by other object) on anUserSession. The<br>
>> > uggly<br>
>> > of 2 is that I have to pass anUserSession as argument.<br>
>> > Either way works well, is really the same?<br>
>> > Thanks in advance,<br>
>> > Facu<br>
>> > (*) I eliminate aBlock for absent elements for this example<br>
>> > _______________________________________________<br>
>> > Magma mailing list<br>
>> > <a href="mailto:Magma@lists.squeakfoundation.org" target="_blank">Magma@lists.squeakfoundation.org</a><br>
>> > <a href="http://lists.squeakfoundation.org/mailman/listinfo/magma" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/magma</a><br>
>> ><br>
>> ><br>
><br>
><br>
</div></div></blockquote></div></div></div><br>
</blockquote></div><br></div>