You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Leo Simons <ls...@jicarilla.org> on 2004/07/08 10:52:56 UTC

[brutus] webapp - why?

Hi gang!

could someone explain to me exactly *why* we're running forrest as a 
webapp? It's a relatively big resource hog...

Looking at our resource usage, we have the following:

load average: 0.97, 1.01, 1.31
Tasks: 112 total,   2 running, 110 sleeping,   0 stopped,   0 zombie
Cpu(s):  23.9% user,   2.2% system,   0.0% nice,  73.9% idle
Mem:   2069676k total,  1994204k used,    75472k free,   253520k buffers
Swap:  4289240k total,    14164k used,  4275076k free,  1032492k cached
 
 

   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
22386 gump       9   0  105m 102m 9984 S  0.0  5.1   0:08.37 java
22387 gump       9   0  105m 102m 9984 S  0.0  5.1   0:00.97 java
22388 gump       9   0  105m 102m 9984 S  0.0  5.1   4:28.08 java
(...)

in other words, that's a lot of tomcat processes with a lot of resident 
memory. From just hitting refresh a lot against the webapp, I suspect 
brutus actually slows to a crawl if -- for example -- there's more than 
a few concurrent users, or some web bot is indexing the gump space.

cheers,

- Leo

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org


Re: [brutus] webapp - why?

Posted by Nicola Ken Barozzi <ni...@apache.org>.
Adam R. B. Jack wrote:
...
> Since we'd rather spend the resources on building than presentation, perhaps
> we ought just move to the XHTML option (in CleanUp branch).

+1

Forrest should be an option, not a strictly necessary dependency.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org


Re: [brutus] webapp - why?

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> could someone explain to me exactly *why* we're running forrest as a
> webapp? It's a relatively big resource hog...

Recall when we ran forrest as a batch command? It would generate thousands
of pages (costing lots of resources) even if those pages were never viewed.
Basically, from what you say, both ways of using Forrest are expensive.

Since we'd rather spend the resources on building than presentation, perhaps
we ought just move to the XHTML option (in CleanUp branch).

regards,

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org


Re: [brutus] webapp - why?

Posted by Leo Simons <ls...@jicarilla.org>.
Stefan Bodewig wrote:
> On Thu, 08 Jul 2004, Leo Simons <ls...@jicarilla.org> wrote:
> 
>>in other words, that's a lot of tomcat processes with a lot of
>>resident memory.
> 
> Sure its not only a lot of Java threads in a single process with a lot
> of resident memory?  Linux process watching tools are unusable WRT
> threads - some people say Linux threads are unusable.

reasonably sure. Other tasks running concurrently are noticably faster 
when tomcat is off. Restarting tomcat also helps tremendously. I just 
tried that and then we're indeed down to just having many dupped threads.

I'm guessing the forrest webapp has a memory leak or two.

- LSD

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org


Re: [brutus] webapp - why?

Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 08 Jul 2004, Leo Simons <ls...@jicarilla.org> wrote:

> in other words, that's a lot of tomcat processes with a lot of
> resident memory.

Sure its not only a lot of Java threads in a single process with a lot
of resident memory?  Linux process watching tools are unusable WRT
threads - some people say Linux threads are unusable.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org