On 7/2/07, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
> What is the initial memory size of the process when it is first
> started? In other words, does it start out this large or grow over
> time?
>
> Have you identified whether it is requests against specific URLs
> within your application which
On Jul 1, 10:43 pm, "Vladimir Pouzanov" <[EMAIL PROTECTED]> wrote:
> $ grep Vm /proc/9453/status
> VmPeak:54556 kB
> VmSize:54552 kB
> VmLck: 0 kB
> VmHWM: 9804 kB
> VmRSS: 9804 kB
> VmData:48160 kB
> VmStk: 128 kB
> VmExe: 4 kB
> VmLib: 5528 kB
> V
On Jul 1, 8:17 pm, [EMAIL PROTECTED] wrote:
> Every django app grabs ~60mb of RAM. I'm currently running three
> different django fcgi processes and that uses half of my available
> RAM.
What is the initial memory size of the process when it is first
started? In other words, does it start out thi
$ grep Vm /proc/9453/status
VmPeak:54556 kB
VmSize:54552 kB
VmLck: 0 kB
VmHWM: 9804 kB
VmRSS: 9804 kB
VmData:48160 kB
VmStk: 128 kB
VmExe: 4 kB
VmLib: 5528 kB
VmPTE:60 kB
settings.DEBUG = False
settings.TEMPLATE_DEBUG = False
On 7/1/07, Ti
>> Every django app grabs ~60mb of RAM. I'm currently running three
>> different django fcgi processes and that uses half of my available
>> RAM.
>
> I'm kind of curious what you're doing with all that RAM ;)
Sounds almost like the classic case of not turning off DEBUG
settings, and having quer
On 7/1/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Every django app grabs ~60mb of RAM. I'm currently running three
> different django fcgi processes and that uses half of my available
> RAM.
I'm kind of curious what you're doing with all that RAM ;)
I run my blog on FastCGI, with a fair
Every django app grabs ~60mb of RAM. I'm currently running three
different django fcgi processes and that uses half of my available
RAM.
On 7/1/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
>
> Jeremy Dunck wrote:
> > Two settings files being used by a single process?
> >
> > How would that work?
Jeremy Dunck wrote:
> Two settings files being used by a single process?
>
> How would that work?
Oh... I missed the bit about a single process. But now I wonder why
require this? One server can happily serve two sites either from
separate mod_python handlers or separate FastCGI servers.
Vlad
On 6/30/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
>
> Vladimir Pouzanov wrote:
> serve both sites from one django process.
>
> Why not just have two settings files?
Two settings files being used by a single process?
How would that work?
--~--~-~--~~~---~--~~
Y
Vladimir Pouzanov wrote:
> Hi all,
>
> I have two sites that run nearly identical django instances. I wonder
> if it's possible to somehow set per-domain ROOT_URLCONF and
> TEMPLATE_DIRS to serve both sites from one django process.
Why not just have two settings files
On Sat, 2007-06-30 at 07:29 -0500, Jeremy Dunck wrote:
> On 6/30/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> >
> ...
> > No, this isn't possible. The settings file is read once and then the
> > settings are cached (and are assumed to be static).
>
> Actually, it *is* possible to alter the
On 6/30/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
...
> No, this isn't possible. The settings file is read once and then the
> settings are cached (and are assumed to be static).
Actually, it *is* possible to alter the urlconf that's processed on a
per-request basis, though TEMPLATE_DIR
On Sat, 2007-06-30 at 14:38 +0300, Vladimir Pouzanov wrote:
> Hi all,
>
> I have two sites that run nearly identical django instances. I wonder
> if it's possible to somehow set per-domain ROOT_URLCONF and
> TEMPLATE_DIRS to serve both sites from one django process.
>
Hi all,
I have two sites that run nearly identical django instances. I wonder
if it's possible to somehow set per-domain ROOT_URLCONF and
TEMPLATE_DIRS to serve both sites from one django process.
--
Sincerely,
Vladimir "Farcaller" Pouzanov
http
14 matches
Mail list logo
