C# program takes 8 seconds to start as cgi process

[The Last Danish Pastry]

Why might IIS 5.1 take a long time (8 seconds) to start a C# console
application as a CGI process, but run a Delphi console app that does
the same thing in no time at all?

Apache2 starts and runs the same C# console app as a CGI immediately.

The C# app and Delphi application both send the same, minimal, output
back to the webserver.

Both applications start as normal, and quickly, from Explorer.

Thanks

--
Clive Tooth
www.clivetooth.dk

[Kevin Spencer]

C# is managed .Net code. It must be compiled at run-time to native machine
language.

The upside is that, once compiled, it is cached. Subsequent calls are nearly
as fast as any native code application. There are many optimizations in the
platform. The trade-off is the benefits of managed code, RAD, and the .Net
platform.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
A watched clock never boils.

"The Last Danish Pastry" <cl****@gmail.com> wrote in message
news:3s************@individual.net...

Why might IIS 5.1 take a long time (8 seconds) to start a C# console
application as a CGI process, but run a Delphi console app that does the
same thing in no time at all?

Apache2 starts and runs the same C# console app as a CGI immediately.

The C# app and Delphi application both send the same, minimal, output back
to the webserver.

Both applications start as normal, and quickly, from Explorer.

Thanks

--
Clive Tooth
www.clivetooth.dk

[The Last Danish Pastry]

"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:OD*************@TK2MSFTNGP15.phx.gbl...

C# is managed .Net code. It must be compiled at run-time to native
machine language.

The upside is that, once compiled, it is cached. Subsequent calls
are nearly as fast as any native code application. There are many
optimizations in the platform. The trade-off is the benefits of
managed code, RAD, and the .Net platform.
Thanks for that. But...

This C# console app is very small. If I compile it and then double
click it from Explorer it has finished within a second. But every time
it starts in the IIS/cgi world it takes 8 seconds to get going. I do
not understand why...

--
Clive Tooth
www.clivetooth.dk

"The Last Danish Pastry" <cl****@gmail.com> wrote in message
news:3s************@individual.net...

Why might IIS 5.1 take a long time (8 seconds) to start a C#
console application as a CGI process, but run a Delphi console app
that does the same thing in no time at all?

Apache2 starts and runs the same C# console app as a CGI
immediately.

The C# app and Delphi application both send the same, minimal,
output back to the webserver.

Both applications start as normal, and quickly, from Explorer.

[Kevin Spencer]

If you were talking about using it in an ASP.Net application, I could
probably tell you. But as you're running it under a CGI process, I don't
know. I can only guess that maybe there is some Interop going on, and
Interop is expensive. I avoid it at all cost.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
A watched clock never boils.

"The Last Danish Pastry" <cl****@gmail.com> wrote in message
news:3s************@individual.net...

"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:OD*************@TK2MSFTNGP15.phx.gbl...

C# is managed .Net code. It must be compiled at run-time to native
machine language.

The upside is that, once compiled, it is cached. Subsequent calls are
nearly as fast as any native code application. There are many
optimizations in the platform. The trade-off is the benefits of managed
code, RAD, and the .Net platform.

Thanks for that. But...

This C# console app is very small. If I compile it and then double click
it from Explorer it has finished within a second. But every time it starts
in the IIS/cgi world it takes 8 seconds to get going. I do not understand
why...

--
Clive Tooth
www.clivetooth.dk

"The Last Danish Pastry" <cl****@gmail.com> wrote in message
news:3s************@individual.net...

Why might IIS 5.1 take a long time (8 seconds) to start a C# console
application as a CGI process, but run a Delphi console app that does the
same thing in no time at all?

Apache2 starts and runs the same C# console app as a CGI immediately.

The C# app and Delphi application both send the same, minimal, output
back to the webserver.

Both applications start as normal, and quickly, from Explorer.

[Peter Bromberg [C# MVP]]

This article by Justin Williams should be helpful:

http://www.codeproject.com/csharp/cgi_csharp.asp

Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"The Last Danish Pastry" wrote:

Why might IIS 5.1 take a long time (8 seconds) to start a C# console
application as a CGI process, but run a Delphi console app that does
the same thing in no time at all?

Apache2 starts and runs the same C# console app as a CGI immediately.

The C# app and Delphi application both send the same, minimal, output
back to the webserver.

Both applications start as normal, and quickly, from Explorer.

Thanks

--
Clive Tooth
www.clivetooth.dk

[Fernando Monteiro]

Hi, Clive !

Why might IIS 5.1 take a long time (8 seconds) to start a C# console
application as a CGI process, but run a Delphi console app that does
the same thing in no time at all?

Apache2 starts and runs the same C# console app as a CGI immediately.

The C# app and Delphi application both send the same, minimal, output
back to the webserver.

Both applications start as normal, and quickly, from Explorer.

Have you heard about HTTP Handlers and modules ?

Check about them at:

http://www.15seconds.com/issue/020417.htm

I think the best approach to have a CGI feature without using ASP.NET is using a
handler.

Regards,

Fernando Monteiro