<br><br><div class="gmail_quote">On Sun, May 29, 2011 at 10:55 AM, Philippe Marschall <span dir="ltr"><<a href="mailto:philippe.marschall@gmail.com">philippe.marschall@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2011/5/28 Mariano Martinez Peck <<a href="mailto:marianopeck@gmail.com">marianopeck@gmail.com</a>>:<br>
<div class="im">><br>
>><br>
>> > What are the errors that I must avoid making ?<br>
>><br>
>> AFAIK SqueakDBX uses FFI which to my understanding means that it calls<br>
>> block the entire VM. That reduces the amount of concurrency a single<br>
>> image can handle. It also makes a connection pool more important.<br>
>><br>
><br>
> Yes, FFI blocks the whole VM while a functions is being called. However, if<br>
> and only if the database client library supports asynchronous queries,<br>
> SqueakDBX will work asynchronously. Basically, we do a loop where we ask the<br>
> backend if the query was ready. If it was not, we do a yield (we let other<br>
> process of the image to run) and then continue the loop.<br>
<br>
</div>How do you avoid turning this into busy awaiting and still manage to<br>
get woken up when data is available?<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div><br>What we do is <br><br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div class="h5">
Cheers<br>
Philippe<br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>