Smalltalk › Frameworks & Tools › Seaside › Seaside General

RE: [Vm-dev] Image Freezing

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Ron Teitelbaum

RE: [Vm-dev] Image Freezing

It may not but it does alleviate the symptom! It's very difficult to work
when the image freezes. The image has been running now for a few hours I
also started seaside and it is still responsive even after long periods of
inactivity.

Ron

> -----Original Message-----
> From: Lukas Renggli [mailto:[hidden email]]
> Sent: Thursday, October 26, 2006 4:34 PM
> To: [hidden email]; Squeak Virtual Machine Development Discussion
> Subject: Re: [Vm-dev] Image Freezing
>
> > Does this process have to run at the same priority as idle? Is there a
> > problem with a deadlock in the priority switching process of the vm?
>
> No, it probably shouldn't run at the same priority (I just chose the
> lowest priority and didn't think more about that). The latest version
> increases this priority to 20. But still, this doesn't solve the
> original problem ...
>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Vincent Girard-Reydet

Performance problems with simple multipart POST requests

Hi all,

Does anyone know of performance problems with Squeak 3.9a / seaside in
handling multipart POST requests ?

I have a simple component plugged on the entrypoint "/seaside/login".
The component accepts POST data, and returns XML. The component derives
from WAEntrypoint.

When I invoke it with URL encoded format:
curl -d "login=toto" -d "password=titi" http://myserver/seaside/login
I get a response time < 0.5s (I haven't done precise profiling).

When I invoke it with multipart format:
curl -F "login=toto" -F "password=titi" http://myserver/seaside/login
I get a response time > 2s !!!!

Using halt points I have seen that most of the processing time is due to
seaside processing the request parameters. It takes almost 2s to get to
the #handleRequest: message of my component with the multipart invokation.

Does any one have tests to suggests and ideas on why it takes so long to
seaside processing such simple parameters ?

Thanks.

Vincent Girard-Reydet
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Philippe Marschall

Re: Performance problems with simple multipart POST requests

2006/10/27, Vincent Girard-Reydet <[hidden email]>:

> Hi all,
>
> Does anyone know of performance problems with Squeak 3.9a / seaside in
> handling multipart POST requests ?
>
> I have a simple component plugged on the entrypoint "/seaside/login".
> The component accepts POST data, and returns XML. The component derives
> from WAEntrypoint.
>
> When I invoke it with URL encoded format:
> curl -d "login=toto" -d "password=titi" http://myserver/seaside/login
> I get a response time < 0.5s (I haven't done precise profiling).
>
> When I invoke it with multipart format:
> curl -F "login=toto" -F "password=titi" http://myserver/seaside/login
> I get a response time > 2s !!!!
>
> Using halt points I have seen that most of the processing time is due to
> seaside processing the request parameters. It takes almost 2s to get to
> the #handleRequest: message of my component with the multipart invokation.
>
> Does any one have tests to suggests and ideas on why it takes so long to
> seaside processing such simple parameters ?

It would certainly help if you could do some more profiling:
https://lists.wisc.edu/read/messages?id=1411189

Cheers
Philippe
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside