[EMAIL PROTECTED] wrote:
> Hello,
>
> i am just wondering myself: this has nothing to with "copy on write"?
> or does that not exist on neither platform?
COW is only relevent when a process forks and the OS can make decisions
about whether memory can be shared between the two processes. He hasn
Hello,
i am just wondering myself: this has nothing to with "copy on write"?
or does that not exist on neither platform?
regards,
usleep
On 4/6/06, Bill Moran <[EMAIL PROTECTED]> wrote:
> "Karl Ma" <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I have a python program in freebsd, doing a heavey ind
"Karl Ma" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a python program in freebsd, doing a heavey indexing job involving a
> mega size array.
>
> The process is so memory-hungry that it starts swap after the physical RAM
> max out. (To be exact, I've lowered the per-process limitation to make thi
Karl Ma wrote:
The process is so memory-hungry that it starts swap after the physical RAM
max out. (To be exact, I've lowered the per-process limitation to make this
possible).
What did you lower, exactly? If you reduce the max resident datasize
needlessly, you're going to make your program s
running for more than a few hours.
In Windows XP, which has less per-task resource restriction (I guess?), I
did successfully complete the task on the same hardware machine; although it
takes more than 30 mins.
How can I push up the priority of the whole paging task? How can I
this will not spe
On Thu, Apr 06, 2006 at 04:43:42PM +0800, Karl Ma wrote:
> Hi,
>
> I have a python program in freebsd, doing a heavey indexing job involving a
> mega size array.
>
> The process is so memory-hungry that it starts swap after the physical RAM
> max out. (To be exact, I've lowered the per-process li