On 4/10/07, A.J.Mechelynck <[EMAIL PROTECTED]> wrote:
Zdenek Sekera wrote:
>
>> -----Original Message-----
>> From: A.J.Mechelynck [mailto:[EMAIL PROTECTED]
>> Sent: 10 April 2007 09:10
>> To: Zdenek Sekera
>> Cc: Yakov Lerner; vim@vim.org; Meino Christian Cramer; Bram Moolenaar
>> Subject: Re: Vim freezes system ?!
>>
>> Zdenek Sekera wrote:
>> [...]
>>> Just to add more to the confusion, on my box (RedHat Enterprise
>> Linux,
>>> 512Mb Ram) I have
>>>
>>> maxmapdepth=1000
>>> maxmempattern=1000
>>> maxmem=257676
>>> maxmemtot=257676
>>>
>>> Which tells me the last two can hardly be in kb and all over I don't
>>> understand what really they mean.
>>>
>>> ---Zdenek
>>>
>>>
>> According to the help, they _are_ in KB and can reach up to two million
>> (i.e.,
>> 2 gig). I sure wonder according to what Vim sets themat startup.
>>
>> Why do you think they can't be in KB? The above would mean slightly
>> over 256
>> meg, which sounds "reasonable" for a 512MB box (more reasonable at
>> least, than
>> the "249 K" which I see).
>
> Arrgh, I guess the batteries in my mental calculator are flat after
> Easter vac :-).
> But what do these numbers really mean? You are right that mine look
> more acceptable than yours. Yours are really strange.
>
> ---Zdenek
Maybe there has been an arithmetic wraparound in my case? I have 2 gig of RAM
installed, which is slightly /more/ than 2 million KB.
I tried it on the machine with 8GB of RAM. The 'mmt' values are 1024.
By the vimhelp, these values are in KB, as Tony said.
Another strange thing is:
these "low" values do not seem to have any effect on vim rmemory usage.
Nor when they are "correct" (like 643272 on 1.3 G ram machine),
neither when they are suspicously low (like 1024 on 8G ram machine).
--
Yakov "look, these numbers are suspicously low" Lerner
