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%
On Thu, 08 Jul 2004, Leo Simons [EMAIL PROTECTED] 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
Stefan Bodewig wrote:
On Thu, 08 Jul 2004, Leo Simons [EMAIL PROTECTED] 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
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,
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 [EMAIL PROTECTED]
