PDA

View Full Version : Poor web application server performance



Mark Rutherford
21-Dec-2005, 02:22 PM
Well, the subject says it all.
The performance is sub-par.

The IIS machine sits behind an Apache reverse proxy.
This is not where the culprit lies.

If you browse to the machine itself, not going thru the reverse proxy
its just as slow. once its initially loaded the page loads are just
fine. it appears that the culprit is the spawning of the 'webapp.exe'
process because I can see that once this process loads that it works
fine. this process simply spawns too slowly.

My thought is that the data is on a fileserver, not local.. and its
causing this?
BUT.. There are no network preformance problems, it just appears that
the process spawns too slowly.
The webapp.exe executable is local.

So, now that I have tinkered with this... I have noted that the way this
works is just contrary to what I have ever done in C (yeah I know this
is vdf..)

Why is there not x number of webapp.exe processes just waiting for
requests? IIS has children waiting .... Apache does...
Why not the webapps? it would eliminate this issue im having, and
probably speed the thing up.

Any speed suggestions? (btw box is pretty fast.. Athlon xp 2800 with 1gb
ram, windows xp sp2, ect.. plenty fast)

Ian Telfer
21-Dec-2005, 05:31 PM
Mark,

Turn on process pooling, that's what you're talking about. When the box
starts up, x number of WebApp.exe processes start and sit there ready
and waiting.

Ian


Mark Rutherford wrote:
> Well, the subject says it all.
> The performance is sub-par.
>
> The IIS machine sits behind an Apache reverse proxy.
> This is not where the culprit lies.
>
> If you browse to the machine itself, not going thru the reverse proxy
> its just as slow. once its initially loaded the page loads are just
> fine. it appears that the culprit is the spawning of the 'webapp.exe'
> process because I can see that once this process loads that it works
> fine. this process simply spawns too slowly.
>
> My thought is that the data is on a fileserver, not local.. and its
> causing this?
> BUT.. There are no network preformance problems, it just appears that
> the process spawns too slowly.
> The webapp.exe executable is local.
>
> So, now that I have tinkered with this... I have noted that the way this
> works is just contrary to what I have ever done in C (yeah I know this
> is vdf..)
>
> Why is there not x number of webapp.exe processes just waiting for
> requests? IIS has children waiting .... Apache does...
> Why not the webapps? it would eliminate this issue im having, and
> probably speed the thing up.
>
> Any speed suggestions? (btw box is pretty fast.. Athlon xp 2800 with 1gb
> ram, windows xp sp2, ect.. plenty fast)

Mark Rutherford
21-Dec-2005, 06:40 PM
That was exactly it. RTFM?

DAW: can you default this behavior? it only speeds it up 1000%.
I thought I had a real issue with it :D

Ian Telfer wrote:
> Mark,
>
> Turn on process pooling, that's what you're talking about. When the box
> starts up, x number of WebApp.exe processes start and sit there ready
> and waiting.
>
> Ian
>
>
> Mark Rutherford wrote:
>> Well, the subject says it all.
>> The performance is sub-par.
>>
>> The IIS machine sits behind an Apache reverse proxy.
>> This is not where the culprit lies.
>>
>> If you browse to the machine itself, not going thru the reverse proxy
>> its just as slow. once its initially loaded the page loads are just
>> fine. it appears that the culprit is the spawning of the 'webapp.exe'
>> process because I can see that once this process loads that it works
>> fine. this process simply spawns too slowly.
>>
>> My thought is that the data is on a fileserver, not local.. and its
>> causing this?
>> BUT.. There are no network preformance problems, it just appears that
>> the process spawns too slowly.
>> The webapp.exe executable is local.
>>
>> So, now that I have tinkered with this... I have noted that the way
>> this works is just contrary to what I have ever done in C (yeah I know
>> this is vdf..)
>>
>> Why is there not x number of webapp.exe processes just waiting for
>> requests? IIS has children waiting .... Apache does...
>> Why not the webapps? it would eliminate this issue im having, and
>> probably speed the thing up.
>>
>> Any speed suggestions? (btw box is pretty fast.. Athlon xp 2800 with
>> 1gb ram, windows xp sp2, ect.. plenty fast)

Marco
21-Dec-2005, 08:10 PM
Mark,

Have more faith in the product...
VDF has quite a bit, the problem is just finding it ;)

Cheers,
Marco

Mark Rutherford wrote:
> That was exactly it. RTFM?
>
> DAW: can you default this behavior? it only speeds it up 1000%.
> I thought I had a real issue with it :D
>
> Ian Telfer wrote:
>
>> Mark,
>>
>> Turn on process pooling, that's what you're talking about. When the
>> box starts up, x number of WebApp.exe processes start and sit there
>> ready and waiting.
>>
>> Ian
>>
>>
>> Mark Rutherford wrote:
>>
>>> Well, the subject says it all.
>>> The performance is sub-par.
>>>
>>> The IIS machine sits behind an Apache reverse proxy.
>>> This is not where the culprit lies.
>>>
>>> If you browse to the machine itself, not going thru the reverse proxy
>>> its just as slow. once its initially loaded the page loads are just
>>> fine. it appears that the culprit is the spawning of the 'webapp.exe'
>>> process because I can see that once this process loads that it works
>>> fine. this process simply spawns too slowly.
>>>
>>> My thought is that the data is on a fileserver, not local.. and its
>>> causing this?
>>> BUT.. There are no network preformance problems, it just appears that
>>> the process spawns too slowly.
>>> The webapp.exe executable is local.
>>>
>>> So, now that I have tinkered with this... I have noted that the way
>>> this works is just contrary to what I have ever done in C (yeah I
>>> know this is vdf..)
>>>
>>> Why is there not x number of webapp.exe processes just waiting for
>>> requests? IIS has children waiting .... Apache does...
>>> Why not the webapps? it would eliminate this issue im having, and
>>> probably speed the thing up.
>>>
>>> Any speed suggestions? (btw box is pretty fast.. Athlon xp 2800 with
>>> 1gb ram, windows xp sp2, ect.. plenty fast)

Mark Rutherford
21-Dec-2005, 10:01 PM
Its not lost faith, I just looked that stuff over and according to the
help its the suggested thing to do, its just not a default.

I think it should be, I would not have known it was there
(I may have eventually found it)
I guess I knew it was there, because for some reason now I have in my
head that Stephen was going over this in some vdf revision at MMISL one
year in the past.
I could be wrong about that.

Now I know(again), I got the memo I just choose to ignore it <vbg>

-Mark

Marco Kuipers wrote:
> Mark,
>
> Have more faith in the product...
> VDF has quite a bit, the problem is just finding it ;)
>
> Cheers,
> Marco
>
> Mark Rutherford wrote:
>> That was exactly it. RTFM?
>>
>> DAW: can you default this behavior? it only speeds it up 1000%.
>> I thought I had a real issue with it :D
>>
>> Ian Telfer wrote:
>>
>>> Mark,
>>>
>>> Turn on process pooling, that's what you're talking about. When the
>>> box starts up, x number of WebApp.exe processes start and sit there
>>> ready and waiting.
>>>
>>> Ian
>>>
>>>
>>> Mark Rutherford wrote:
>>>
>>>> Well, the subject says it all.
>>>> The performance is sub-par.
>>>>
>>>> The IIS machine sits behind an Apache reverse proxy.
>>>> This is not where the culprit lies.
>>>>
>>>> If you browse to the machine itself, not going thru the reverse
>>>> proxy its just as slow. once its initially loaded the page loads are
>>>> just fine. it appears that the culprit is the spawning of the
>>>> 'webapp.exe' process because I can see that once this process loads
>>>> that it works fine. this process simply spawns too slowly.
>>>>
>>>> My thought is that the data is on a fileserver, not local.. and its
>>>> causing this?
>>>> BUT.. There are no network preformance problems, it just appears
>>>> that the process spawns too slowly.
>>>> The webapp.exe executable is local.
>>>>
>>>> So, now that I have tinkered with this... I have noted that the way
>>>> this works is just contrary to what I have ever done in C (yeah I
>>>> know this is vdf..)
>>>>
>>>> Why is there not x number of webapp.exe processes just waiting for
>>>> requests? IIS has children waiting .... Apache does...
>>>> Why not the webapps? it would eliminate this issue im having, and
>>>> probably speed the thing up.
>>>>
>>>> Any speed suggestions? (btw box is pretty fast.. Athlon xp 2800 with
>>>> 1gb ram, windows xp sp2, ect.. plenty fast)

Vincent Oorsprong
22-Dec-2005, 03:02 AM
Mark,

Be aware that for turning on this switch your application must be ready to
handle it correctly. Each ASP file that is being executed can be handled by
a different webapp.exe. This means a 100+% no-no for persisent settings like
record buffers and properties. It is great feature when you did your
programming work right but just turn on can be dangerous.

PS: We advise to turn it on for webservices. Else each call starts a
webapp.exe and stops it too again.

--
Regards,
Vincent Oorsprong
Data Access Europe B.V.
http://www.dataaccess.nl
Tel: +31-74-2555609

Mark Rutherford
22-Dec-2005, 09:52 AM
Thanks for telling me but I assumed that it did this already so that is
how I designed it :)

I did not know it was not on by default.
I would encorage anyone to use it this way, its superior to the other way :D


Vincent Oorsprong wrote:
> Mark,
>
> Be aware that for turning on this switch your application must be ready to
> handle it correctly. Each ASP file that is being executed can be handled by
> a different webapp.exe. This means a 100+% no-no for persisent settings like
> record buffers and properties. It is great feature when you did your
> programming work right but just turn on can be dangerous.
>
> PS: We advise to turn it on for webservices. Else each call starts a
> webapp.exe and stops it too again.
>