Re: Linux Application Disk and Memory Usage
- From: Keith Keller <kkeller-usenet@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 2 Aug 2007 10:15:56 -0700
On 2007-08-02, Kushal <kushal.agarwal@xxxxxxxxx> wrote:
2. Dynamic dispace = maximum space need to accomodate log file, temp
files, etc.
This varies wildly based on both the application itself and the
particular policies of the system (e.g., log rotation). If your
application doesn't purge its log file itself, then in theory the
''maximum'' space is the size of the filesystem! So for this particular
requirement, you need to decide for what typical usages you want to
determine these numbers, and then either run your app under those
conditions, or from your knowledge of the code compute the sizes of
these resources. AFAIK there's no tool which will do that without your
intervention.
You should also evaluate failure modes: if a user does a kill -9 on your
app, what happens to the files that get left behind? If your normal
policy is to clean up disk resources, but it can't because of a hard
kill or reset, will the app be able to clean them up next time it
starts, or will they sit around and eat space? (Or worse, prevent the
app from starting?)
--keith
--
kkeller-usenet@xxxxxxxxxxxxxxxxxxxxxxxxxx
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information
.
- Follow-Ups:
- Re: Linux Application Disk and Memory Usage
- From: Jean-David Beyer
- Re: Linux Application Disk and Memory Usage
- References:
- Linux Application Disk and Memory Usage
- From: Kushal
- Re: Linux Application Disk and Memory Usage
- From: Dan Espen
- Re: Linux Application Disk and Memory Usage
- From: Kushal
- Linux Application Disk and Memory Usage
- Prev by Date: Re: Linux Application Disk and Memory Usage
- Next by Date: Re: Firefox and Cygwin
- Previous by thread: Re: Linux Application Disk and Memory Usage
- Next by thread: Re: Linux Application Disk and Memory Usage
- Index(es):
Relevant Pages
|