seaside performance in Squeak

> Hi,
>
> I think this is very great news and can I get the source or binary  
> of VM(windows)
> for this? Or should I do this by myself?
>
> Thanks in advance.
>
> ----- Original Message -----
>   From: John M McIntosh <[hidden email]>
>   To: Seaside - general discussion  
> <[hidden email]>
>   Sent: 07-11-20 05:52:49
>   Subject: [Seaside] seaside performance in Squeak
>
>  James is busy blogging on seaside squeak, VW, rubyonrails performance
> and I'll note that a bit of Squeak GC tuning can
> improve squeak seaside thruput by 100%
>
> http://www.cincomsmalltalk.com/blog/blogView?showComments=true&printTitle=More_Seaside_Testing&entry=3372921925

> Hi,
>
> I've modified source code manually by referring http://bugs.squeak.org/view.php?id=6667 
> ,
> but I'm not sure whether modifying referred part is OK. It seems  
> that the code built without
> problem, and run correctly up to now :-)
>
> Should I regenerated all VM code instead of doing above?
>
> Thanks in advance.
>
> ----- Original Message -----
>   From: John M McIntosh <[hidden email]>
>   To: Seaside - general discussion  
> <[hidden email]>
>   Sent: 07-11-20 15:22:27
>   Subject: Re: [Seaside] seaside performance in Squeak
>
>  http://www.squeakvm.org/win32/
>
> you could talk to who ever built the current windows VM you have and
> see if it was built with VMMaker-tpr.63
> also see
> http://wiki.sq 
> Vhay5vcmcvc3F1ZWFrLzIxMDUNCg0KQSBWTU1ha2VyIGltYWdlIHRvIGJ1aWxkIGEgVk0g
> bXVzdCBoYXZlIHRoZSBmaXhlZCBjb2RlIGFzIGRldGFpbGVkIGluDQpodHRwOi8vYnVncy5zcXVlYWsub3JnL3ZpZXcucGhwP2lkPTY2NjcNCg0KT3RoZXJ3aXNlIHRoZSB0dW5pbmcgaGludHMgd2lsbCBub3Qgd29yaw0KDQoNCk9uIE5vdiAxOSwgMjAwNywgYXQgNTo1MyBQTSwgY2h1bnNqQGVtYmlhbi5jb20gd3JvdGU6DQoNCj4gSGksDQo+DQo+IEkgdGhpbmsgdGhpcyBpcyB2ZXJ5IGdyZWF0IG5ld3MgYW5kIGNhbiBJIGdldCB0aGUgc291cmNlIG9yIGJpbmFyeSAgDQo+IG9mIFZNKHdpbmRvd3MpDQo+IGZvciB0aGlzPyBPciBzaG91bGQgSSBkbyB0aGlzIGJ5IG15c2VsZj8NCj4NCj4gVGhhbmtzIGluIGFkdmFuY2UuDQo+DQo+IC0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCj4gICBGcm9tOiBKb2huIE0gTWNJbnRvc2ggPGpvaG5tY2lAc21hbGx0YWxrY29uc3VsdGluZy5jb20+DQo+ICAgVG86IFNlYXNpZGUgLSBnZW5lcmFsIGRpc2N1c3Npb24gIA0KPiA8c2Vhc2lkZUBsaXN0cy5zcXVlYWtmb3VuZGF0aW9uLm9yZz4NCj4gICBTZW50OiAwNy0xMS0yMCAwNTo1Mjo0OQ0KPiAgIFN1YmplY3Q6IFtTZWFzaWRlXSBzZWFzaWRlIHBlcmZvcm1hbmNlIGluIFNxdWVhaw0KPg0KPiAgSmFtZXMgaXMgYnVzeSBibG9nZ2luZyBvbiBzZWFzaWRlIHNxdWVhaywgVlcsIHJ1YnlvbnJhaWxzIHBlcmZvcm1hbmN
> lDQo
> +IGFuZCBJJ2xsIG5vdGUgdGhhdCBhIGJpdCBvZiBTcXVlYWsgR0MgdHVuaW5nIGNhbg0KPiBpbXByb3ZlIHNxdWVhayBzZWFzaWRlIHRocnVwdXQgYnkgMTAwJQ0KPg0KPiBodHRwOi8vd3d3LmNpbmNvbXNtYWxsdGFsay5jb20vYmxvZy9ibG9nVmlldz9zaG93Q29tbWVudHM9dHJ1ZSZwcmludFRpdGxlPU1vcmVfU2Vhc2lkZV9UZXN0aW5nJmVudHJ5PTMzNzI5MjE5MjUNCg0KLS0NCj0gDQo9IA0KPSANCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KSm9obiBNLiBNY0ludG9zaCA8am9obm1jaUBzbWFsbHRhbGtjb25zdWx0aW5nLmNvbT4NCkNvcnBvcmF0ZSBTbWFsbHRhbGsgQ29uc3VsdGluZyBMdGQuICBodHRwOi8vd3d3LnNtYWxsdGFsa2NvbnN1bHRpbmcuY29tDQo9IA0KPSANCj0gDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0Kc2Vhc2lkZSBtYWlsaW5nIGxpc3QNCnNlYXNpZGVAbGlzdHMuc3F1ZWFrZm91bmRhdGlvbi5vcmcNCmh0dHA6Ly9saXN0cy5zcXVlYWtmb3VuZGF0aW9uLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vc2Vhc2lkZQ0KDQo=
> u

> http://www.squeakvm.org/win32/
>
> you could talk to who ever built the current windows VM you have and  
> see if it was built with VMMaker-tpr.63
> also see
> http://wiki.squeak.org/squeak/2105
>
> A VMMaker image to build a VM must have the fixed code as detailed in
> http://bugs.squeak.org/view.php?id=6667
>
> Otherwise the tuning hints will not work
>
>
>
> On Nov 19, 2007, at 5:53 PM, [hidden email] wrote:
>
>> Hi,
>>
>> I think this is very great news and can I get the source or binary  
>> of VM(windows)
>> for this? Or should I do this by myself?
>>
>> Thanks in advance.
>>
>> ----- Original Message -----
>>  From: John M McIntosh <[hidden email]>
>>  To: Seaside - general discussion  
>> <[hidden email]>
>>  Sent: 07-11-20 05:52:49
>>  Subject: [Seaside] seaside performance in Squeak
>>
>> James is busy blogging on seaside squeak, VW, rubyonrails performance
>> and I'll note that a bit of Squeak GC tuning can
>> improve squeak seaside thruput by 100%
>>
>> http://www.cincomsmalltalk.com/blog/blogView?showComments=true&printTitle=More_Seaside_Testing&entry=3372921925
>
> --
> =
> =
> =
> =
> =
> ======================================================================
> John M. McIntosh <[hidden email]>
> Corporate Smalltalk Consulting Ltd.  http://
> www.smalltalkconsulting.com
> =
> =
> =
> =
> =
> ======================================================================
>
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

>
> On 23-Nov-07, at 12:09 AM, Alexander Lazarevic' wrote:
>
>> VMMaker-tpr.63
>
>
> Well, *I* have a copy but I'm not sure how anyone else would since I  
> don't usually publish numbered versions.
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> Why do we want intelligent terminals when there are so many stupid  
> users?
>
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

>
> On 23-Nov-07, at 9:00 AM, Adrian Lienhard wrote:
>
> >May I ask why VMMaker is not stored in one dedicated SqueakSource  
> >repository?
>
> Because I tried it once and had problems and never got around to  
> making another attempt.
>
> >It should be a matter of minutes to create a project and commit the  
> >current version to it and then people can commit and merge their  
> >fixes etc.
> You're kidding, yes? The chances of me letting other people commit  
> changes to such an important chunk of code are exactly (no floating  
> point comparison to confuse things) zero.

>
> On 23-Nov-07, at 9:00 AM, Adrian Lienhard wrote:
>
>> May I ask why VMMaker is not stored in one dedicated SqueakSource  
>> repository?
>
> Because I tried it once and had problems and never got around to  
> making another attempt.
>
>> It should be a matter of minutes to create a project and commit the  
>> current version to it and then people can commit and merge their  
>> fixes etc.
> You're kidding, yes?

>> Because I tried it once and had problems and never got around to  
>> making another attempt.
>>
>>> It should be a matter of minutes to create a project and commit  
>>> the current version to it and then people can commit and merge  
>>> their fixes etc.
>> You're kidding, yes?
>
> No, I'm serious. Of course, you are not going to blindly merge  
> everything people commit.  You can skip whatever changes you don't  
> like in your main line. This is how Seaside is done, and I think it  
> works well. The nice thing is that you don't need to mail mcz or cs  
> files around and hence it is more likely that people share changes  
> that are worth being looked at.
> If you don't like this, you can also make the project read only or  
> only writable by the guys you trust. This would allow outsiders to  
> see what is going on.

>
> On 23-Nov-07, at 12:32 PM, Adrian Lienhard wrote:
>
>>> Because I tried it once and had problems and never got around to  
>>> making another attempt.
>>>
>>>> It should be a matter of minutes to create a project and commit  
>>>> the current version to it and then people can commit and merge  
>>>> their fixes etc.
>>> You're kidding, yes?
>>
>> No, I'm serious. Of course, you are not going to blindly merge  
>> everything people commit.  You can skip whatever changes you don't  
>> like in your main line. This is how Seaside is done, and I think it  
>> works well. The nice thing is that you don't need to mail mcz or cs  
>> files around and hence it is more likely that people share changes  
>> that are worth being looked at.
>> If you don't like this, you can also make the project read only or  
>> only writable by the guys you trust. This would allow outsiders to  
>> see what is going on.
>
> Agreed. It works quite well for OmniBrowser too.  I'm picky about  
> what changes I merge into the mainline, but I let anyone save  
> versions to my repository. If people commit code that's problematic,  
> that's fine, it just doesn't get merged into the trunk.