[Seaside] Increasing the performances of a Seaside application

[Mariano Martinez Peck]

On Sun, May 29, 2011 at 10:55 AM, Philippe Marschall <
philippe.marschall at gmail.com> wrote:

> 2011/5/28 Mariano Martinez Peck <marianopeck at gmail.com>:
> >
> >>
> >> > What are the errors that I must avoid making ?
> >>
> >> AFAIK SqueakDBX uses FFI which to my understanding means that it calls
> >> block the entire VM. That reduces the amount of concurrency a single
> >> image can handle. It also makes a connection pool more important.
> >>
> >
> > Yes, FFI blocks the whole VM while a functions is being called. However,
> if
> > and only if the database client library supports asynchronous queries,
> > SqueakDBX will work asynchronously. Basically, we do a loop where we ask
> the
> > backend if the query was ready. If it was not, we do a yield (we let
> other
> > process of the image to run) and then continue the loop.
>
> How do you avoid turning this into busy awaiting and still manage to
> get woken up when data is available?
>
>
What we do is



> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>



-- 
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20110529/594654c1/attachment.htm