recommended available RAM for frontier?

Eric Soroos eric-ul at soroos.net
Tue Mar 4 11:57:56 PST 2003


On Tue, 4 Mar 2003 13:30:05 -0600 in message <008a01c2e284$c33a8d30$1202a8c0 at JoshuaDesktop>, "Joshua Lipton/Slowtrain" <joshua at theslowtrain.com> wrote:

> Frontier itself has got a pretty small footprint... just one manila site
> running and no strange sizes on any of the databases/tables etc.

I thought that there was a memory used indicator on NT, but I may be wrong. 

> No access to the machine itself... but I would ASSUME that an NT server with
> only 128MB of ram is going to be dogging pretty badly... swapping and on
> full CPU load anyway. Frontier isn't the only app being hosted on this
> machine.

I'm guessing that frontier is taking on the order of 10 megs with a minimal websites loaded. (I'm seeing about that for resident size on several of my small systems) That's minimal unless you're having to swap a good portion of that in and out, and on a machine with 128 megs that's a good guess at the performance hit.
 
> What is this echo responder? How does one use the echo page?
> 

http://www.wiredfool.com/echo

It's a very basic responder that just echos the header content of your request. If it's enabled at system.verbs.builtins.webserver.responders.echo.enabled , you should be able to hit it at http://your.server/echo . It's a small page with a lot less overhead than mainresponder/manila.  If its slow, I'd be more inclined to believe that you're being starved for cycles. If it's fast, well, maybe this test doesn't rule that much out. 

It would really be useful to know what frontier's proc/swap/memory usage are from the os as it's running, but I guess you'd need their cooperation for that.

eric

 





More information about the Frontier-Users mailing list