July 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] CameraPlugin for VM

by Bernat Romagosa

By the way, you can also test it by doing: CameraPlugin videoTest The code in this method also helps understand how the camera works. Cheers, 2011/7/29 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > Oops sorry, I accidentally sent it twice. > > The license should be MIT, check out the "The Scratch Source Code License" > section: http://info.scratch.mit.edu/Source_Code > > <http://info.scratch.mit.edu/Source_Code>Although they don't specifically > state what's the license for the Camera Plugin, I guess it just applies by > extension since it belongs to the project and the whole project is MIT. > > If we are to include it in Pharo I suppose we should check it thoroughly... > > Cheers, > > > 2011/7/29 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > >> Hi Torsten, >> >> The plugin works out of the box for me in a Cog machine with no problems, >> just follow these instructions: >> >> * Get Scratch's CameraPlugin (you can get them here >> http://code.google.com/p/scat/downloads/list) >> * Depending on your OS, place it in: >> GNU/Linux and Win32 â The Pharo root directory. That is, where the .sh >> and .lnk files are. >> MacOSX â The image path. >> * FileIn the three .st files I attach (they originally came from the >> Scratch source, but were modified by us to get them working in Pharo) >> * DoIt: ScratchCameraDialog new openCamera; openInWorld >> >> Of course, you don't need the ScratchCameraDialog class, but it's nice to >> have it as it's a pretty simple working example. I'm not sure whether you >> need CameraMedia either, didn't have time to check... >> >> Hope it helps! >> >> Cheers, >> >> 2011/7/29 Torsten Bergmann <astares(a)gmx.de> >> >>> Bernat Romagosa wrote: >>> > In Scat we've managed, maybe after lunch i can give you some directions >>> > to get it running. >>> >>> Yes, I managed to make it work last year, just with the >>> *.cs and the Win32 DLL from scratch. >>> >>> However feel free to post a short guide for the recent Pharo >>> image to the list so others can profit from it. >>> >>> >>> My post was more oriented towards the VM developers >>> since AFAIK there was a discussion of integrating >>> the plugin back into Squeak VM sources so it is >>> available in general to Squeak/Etoys/forks. >>> >>> As Bert wrote: >>> >>> "but the Scratch folks are interested in having their >>> plugins in the main Squeak VM, so they do not have to >>> package and maintain them themselves for ever." >>> >>> Would be nice if one would be able to use the cam >>> out of the box with a recent VM (standard and cog) and Pharo. >>> >>> Thx >>> Torsten >>> -- >>> NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! >>> Jetzt informieren: http://www.gmx.net/de/go/freephone >>> >>> >> >> >> -- >> Bernat Romagosa. >> > > > > -- > Bernat Romagosa. > -- Bernat Romagosa.

July 29, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by Lukas Renggli

> I did some debugging and Swazoo does not seem to support keep-alive with > HTTP 1.0, only with HTTP 1.1. ab unfortunately makes only HTTP 1.0 requests. Ok, but still a bit strange that this breaks Swazoo ... Anyway, I don't care. > There is a Seaside-Benchmark package in Seaside30Addons which is IMHO > better suited for adapter benchmarks because it avoid dynamic allocation. It doesn't matter here, the allocations are the same for every adaptor and also very stable. This was mostly a test to see if the server adaptors don't break with many concurrent request. Lukas -- Lukas Renggli www.lukas-renggli.ch

July 29, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by Philippe Marschall

On 07/29/2011 11:06 AM, Lukas Renggli wrote: > Ok, problem solved. All server adaptors work now. > > A little benchmark for 500 requests (concurrency level 10): > > 1. Zinc -- 2073.80 [Kbytes/sec] received > 2. Kom -- 1857.66 [Kbytes/sec] received > 3. Swzoo -- 1662.48 [Kbytes/sec] received > > Zinc can nicely play out the keep-alive. Kom doesn't support > keep-alive. With Swazoo a lot of requests fail if keep-alive is > enabled (so I disabled it). Details in the attachment. I did some debugging and Swazoo does not seem to support keep-alive with HTTP 1.0, only with HTTP 1.1. ab unfortunately makes only HTTP 1.0 requests. There is a Seaside-Benchmark package in Seaside30Addons which is IMHO better suited for adapter benchmarks because it avoid dynamic allocation. Cheers Philippe

July 29, 2011

Re: [Pharo-project] CameraPlugin for VM

by Bernat Romagosa

Oops sorry, I accidentally sent it twice. The license should be MIT, check out the "The Scratch Source Code License" section: http://info.scratch.mit.edu/Source_Code <http://info.scratch.mit.edu/Source_Code>Although they don't specifically state what's the license for the Camera Plugin, I guess it just applies by extension since it belongs to the project and the whole project is MIT. If we are to include it in Pharo I suppose we should check it thoroughly... Cheers, 2011/7/29 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > Hi Torsten, > > The plugin works out of the box for me in a Cog machine with no problems, > just follow these instructions: > > * Get Scratch's CameraPlugin (you can get them here > http://code.google.com/p/scat/downloads/list) > * Depending on your OS, place it in: > GNU/Linux and Win32 â The Pharo root directory. That is, where the .sh > and .lnk files are. > MacOSX â The image path. > * FileIn the three .st files I attach (they originally came from the > Scratch source, but were modified by us to get them working in Pharo) > * DoIt: ScratchCameraDialog new openCamera; openInWorld > > Of course, you don't need the ScratchCameraDialog class, but it's nice to > have it as it's a pretty simple working example. I'm not sure whether you > need CameraMedia either, didn't have time to check... > > Hope it helps! > > Cheers, > > 2011/7/29 Torsten Bergmann <astares(a)gmx.de> > >> Bernat Romagosa wrote: >> > In Scat we've managed, maybe after lunch i can give you some directions >> > to get it running. >> >> Yes, I managed to make it work last year, just with the >> *.cs and the Win32 DLL from scratch. >> >> However feel free to post a short guide for the recent Pharo >> image to the list so others can profit from it. >> >> >> My post was more oriented towards the VM developers >> since AFAIK there was a discussion of integrating >> the plugin back into Squeak VM sources so it is >> available in general to Squeak/Etoys/forks. >> >> As Bert wrote: >> >> "but the Scratch folks are interested in having their >> plugins in the main Squeak VM, so they do not have to >> package and maintain them themselves for ever." >> >> Would be nice if one would be able to use the cam >> out of the box with a recent VM (standard and cog) and Pharo. >> >> Thx >> Torsten >> -- >> NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! >> Jetzt informieren: http://www.gmx.net/de/go/freephone >> >> > > > -- > Bernat Romagosa. > -- Bernat Romagosa.

July 29, 2011

Re: [Pharo-project] CameraPlugin for VM

by Bernat Romagosa

Hi Torsten, The plugin works out of the box for me in a Cog machine with no problems, just follow these instructions: * Get Scratch's CameraPlugin (you can get them here http://code.google.com/p/scat/downloads/list) * Depending on your OS, place it in: GNU/Linux and Win32 â The Pharo root directory. That is, where the .sh and .lnk files are. MacOSX â The image path. * FileIn the three .st files I attach (they originally came from the Scratch source, but were modified by us to get them working in Pharo) * DoIt: ScratchCameraDialog new openCamera; openInWorld Of course, you don't need the ScratchCameraDialog class, but it's nice to have it as it's a pretty simple working example. I'm not sure whether you need CameraMedia either, didn't have time to check... Hope it helps! Cheers, 2011/7/29 Torsten Bergmann <astares(a)gmx.de> > Bernat Romagosa wrote: > > In Scat we've managed, maybe after lunch i can give you some directions > > to get it running. > > Yes, I managed to make it work last year, just with the > *.cs and the Win32 DLL from scratch. > > However feel free to post a short guide for the recent Pharo > image to the list so others can profit from it. > > > My post was more oriented towards the VM developers > since AFAIK there was a discussion of integrating > the plugin back into Squeak VM sources so it is > available in general to Squeak/Etoys/forks. > > As Bert wrote: > > "but the Scratch folks are interested in having their > plugins in the main Squeak VM, so they do not have to > package and maintain them themselves for ever." > > Would be nice if one would be able to use the cam > out of the box with a recent VM (standard and cog) and Pharo. > > Thx > Torsten > -- > NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! > Jetzt informieren: http://www.gmx.net/de/go/freephone > > -- Bernat Romagosa.

July 29, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by Sven Van Caekenberghe

On 29 Jul 2011, at 11:56, Mariano Martinez Peck wrote: > What is the difference between that and a database connection pool ? A connection pool goes a step further, it keeps on reusing multiple connections that each should be kept alive. The idea is always the same: do caching to avoid expensive setup costs. A higher resource usage is the price to pay. Sven

July 29, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by Marcus Denker

On Jul 29, 2011, at 11:57 AM, Mariano Martinez Peck wrote: > > > On Fri, Jul 29, 2011 at 11:51 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > >> Zinc can nicely play out the keep-alive. Kom doesn't support > >> keep-alive. With Swazoo a lot of requests fail if keep-alive is > >> enabled (so I disabled it). Details in the attachment. > > > > what is keep-alive? > > The server keeps the socket open after a request-response cycle and > allows clients (browsers) to reuse the same socket for multiple > requests. This is typically faster than to open a new socket for each > request. > In addition to not having to set up a new connection, the other thing that is a problem with short lived TCP request is TCP slow-start: http://en.wikipedia.org/wiki/Slow-start A new TCP connection "probes" by sending a little and then it slowly increases. If you use short-lived TCP connections, it can happen that you are never leaving the slow-start discovery phase. Marcus -- Marcus Denker -- http://marcusdenker.de

July 29, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by Sven Van Caekenberghe

On 29 Jul 2011, at 11:06, Lukas Renggli wrote: > Ok, problem solved. All server adaptors work now. > > A little benchmark for 500 requests (concurrency level 10): > > 1. Zinc -- 2073.80 [Kbytes/sec] received > 2. Kom -- 1857.66 [Kbytes/sec] received > 3. Swzoo -- 1662.48 [Kbytes/sec] received > > Zinc can nicely play out the keep-alive. Kom doesn't support > keep-alive. With Swazoo a lot of requests fail if keep-alive is > enabled (so I disabled it). Details in the attachment. > > Glad that we have Zinc as the default server now :-) I am happy and smiling now! Sven

July 29, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by StÃ©phane Ducasse

Tx. I do not know if you saw but Olivier Auverlot built a Socket pool and he got really good results. Mariano told him that openDBX got one already and I should sync with Olivier to know its statuses but he was quite happy with the load he could support using Seaside-REST. Stef On Jul 29, 2011, at 11:51 AM, Lukas Renggli wrote: >>> Zinc can nicely play out the keep-alive. Kom doesn't support >>> keep-alive. With Swazoo a lot of requests fail if keep-alive is >>> enabled (so I disabled it). Details in the attachment. >> >> what is keep-alive? > > The server keeps the socket open after a request-response cycle and > allows clients (browsers) to reuse the same socket for multiple > requests. This is typically faster than to open a new socket for each > request. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

July 29, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by Mariano Martinez Peck

On Fri, Jul 29, 2011 at 11:51 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > >> Zinc can nicely play out the keep-alive. Kom doesn't support > >> keep-alive. With Swazoo a lot of requests fail if keep-alive is > >> enabled (so I disabled it). Details in the attachment. > > > > what is keep-alive? > > The server keeps the socket open after a request-response cycle and > allows clients (browsers) to reuse the same socket for multiple > requests. This is typically faster than to open a new socket for each > request. > > What is the difference between that and a database connection pool ? -- Mariano http://marianopeck.wordpress.com

July 29, 2011