Re: malloc.conf recommended settings

2017-04-02 Thread Steven Schneider

* Otto Moerbeek  [170401 07:30]:

On Sat, Apr 01, 2017 at 03:11:32AM +, Steven Schneider wrote:


Thanks Theo and Otto for replying.


I have a question about the recommended settings for /etc/malloc.conf.  I'm
currently using JUC on my i386 laptop, just to see how the old beast handles
it. I hadn't noticed any significant performance issues though it did crash
Chromium because it was using memory it had just freed. On my amd64 desktop
I am just using J as I was working on some assignments and I didn't want to
try anything too risky until I had completed the assignments.


I'd use at C or S for development. The earlier you discover a problem,
the better. Note that S includes a few other flags.

This makes me wonder what's all included in S. I have a copy of the 
source tree so I guess I have some reading ahead of me. :-)


What are some recommended settings for /etc/malloc.conf in given scenarios
such as general use desktop, or an internet facing webserver?


Just use no malloc.conf, it's te default. If the performance loss is
acceptable (only you can decide that) try S. But as you have seen,
some programs have bugs that are exposed by the flags. Again, only you
can decide if that's acceptable.

I agree that my question was a bit vague, though that wasn't my 
intention, as there being numerous desktop setup one could have. The 
malloc.conf man page recommends U for security and F for debugging and 
it was that entry in the man page that inspired me to ask this question.


Anyhow, thanks for taking the time to answer my somewhat naive 
questions, Theo and Otto. I will play around with the settings a bit, 
read the source and decide what I prefer.


--
W. Steven Schneider  



Re: malloc.conf recommended settings

2017-04-01 Thread Otto Moerbeek
On Sat, Apr 01, 2017 at 03:11:32AM +, Steven Schneider wrote:

> Hi,
> 
> I have a question about the recommended settings for /etc/malloc.conf.  I'm
> currently using JUC on my i386 laptop, just to see how the old beast handles
> it. I hadn't noticed any significant performance issues though it did crash
> Chromium because it was using memory it had just freed. On my amd64 desktop
> I am just using J as I was working on some assignments and I didn't want to
> try anything too risky until I had completed the assignments.

I'd use at C or S for development. The earlier you discover a problem,
the better. Note that S includes a few other flags.

> 
> What are some recommended settings for /etc/malloc.conf in given scenarios
> such as general use desktop, or an internet facing webserver?

Just use no malloc.conf, it's te default. If the performance loss is
acceptable (only you can decide that) try S. But as you have seen,
some programs have bugs that are exposed by the flags. Again, only you
can decide if that's acceptable.

-Otto



Re: malloc.conf recommended settings

2017-03-31 Thread Theo de Raadt
> I have a question about the recommended settings for /etc/malloc.conf.  

Well, by default we ship without the file.

> I'm currently using JUC on my i386 laptop, just to see how the old beast 
> handles it. I hadn't noticed any significant performance issues though it 
> did crash Chromium because it was using memory it had just freed. On my 
> amd64 desktop I am just using J as I was working on some assignments and 
> I didn't want to try anything too risky until I had completed the 
> assignments.
> 
> What are some recommended settings for /etc/malloc.conf in given 
> scenarios such as general use desktop, or an internet facing webserver?

It depends what you want.

If you want to use these features to dynamically discover software
problems, you found a feature other systems don't have.

Otherwise, don't create it.



malloc.conf recommended settings

2017-03-31 Thread Steven Schneider

Hi,

I have a question about the recommended settings for /etc/malloc.conf.  
I'm currently using JUC on my i386 laptop, just to see how the old beast 
handles it. I hadn't noticed any significant performance issues though it 
did crash Chromium because it was using memory it had just freed. On my 
amd64 desktop I am just using J as I was working on some assignments and 
I didn't want to try anything too risky until I had completed the 
assignments.


What are some recommended settings for /etc/malloc.conf in given 
scenarios such as general use desktop, or an internet facing webserver?


Thanks.

--
W. Steven Schneider