Re: Request for testing malloc and multi-threaded applications

2022-09-27 Thread Otto Moerbeek
On Tue, Sep 27, 2022 at 03:31:12PM +0200, Renaud Allard wrote: > On 1/16/19 19:09, Otto Moerbeek wrote: > > On Wed, Jan 16, 2019 at 01:25:25PM +, Stuart Henderson wrote: > > > > > On 2019/01/04 08:09, Otto Moerbeek wrote: > > > > On Thu, Dec 27, 2018 at 09:39:56AM +0100, Otto Moerbeek wrote:

Re: Request for testing malloc and multi-threaded applications

2022-09-27 Thread Renaud Allard
On 1/16/19 19:09, Otto Moerbeek wrote: On Wed, Jan 16, 2019 at 01:25:25PM +, Stuart Henderson wrote: On 2019/01/04 08:09, Otto Moerbeek wrote: On Thu, Dec 27, 2018 at 09:39:56AM +0100, Otto Moerbeek wrote: Very little feedback so far. This diff can only give me valid feedback if the cov

Re: Request for testing malloc and multi-threaded applications

2019-01-18 Thread Otto Moerbeek
On Fri, Jan 18, 2019 at 08:41:57AM +0100, Alexandr Nedvedicky wrote: > Hello Otto, > > I gave it a try with firefox. according to my subjective tests > I could not spot any differences with various setting. > > I've decided to try with some memory benchmarks I could find on github [1]. I > did c

Re: Request for testing malloc and multi-threaded applications

2019-01-17 Thread Alexandr Nedvedicky
Hello Otto, I gave it a try with firefox. according to my subjective tests I could not spot any differences with various setting. I've decided to try with some memory benchmarks I could find on github [1]. I did create a fork [2] with my own test runner to try out your diff. To run it just do som

Re: Request for testing malloc and multi-threaded applications

2019-01-16 Thread Stuart Henderson
On 2019/01/16 19:09, Otto Moerbeek wrote: > On Wed, Jan 16, 2019 at 01:25:25PM +, Stuart Henderson wrote: > > > On 2019/01/04 08:09, Otto Moerbeek wrote: > > > On Thu, Dec 27, 2018 at 09:39:56AM +0100, Otto Moerbeek wrote: > > > > > > > > > > > Very little feedback so far. This diff can only

Re: Request for testing malloc and multi-threaded applications

2019-01-16 Thread Otto Moerbeek
On Wed, Jan 16, 2019 at 01:25:25PM +, Stuart Henderson wrote: > On 2019/01/04 08:09, Otto Moerbeek wrote: > > On Thu, Dec 27, 2018 at 09:39:56AM +0100, Otto Moerbeek wrote: > > > > > > > > Very little feedback so far. This diff can only give me valid feedback > > > if the coverage of systems

Re: Request for testing malloc and multi-threaded applications

2019-01-16 Thread Stuart Henderson
On 2019/01/04 08:09, Otto Moerbeek wrote: > On Thu, Dec 27, 2018 at 09:39:56AM +0100, Otto Moerbeek wrote: > > > > > Very little feedback so far. This diff can only give me valid feedback > > if the coverage of systems and use cases is wide. If I do not get > > more feedback, I have to base my d

Re: Request for testing malloc and multi-threaded applications

2019-01-03 Thread Otto Moerbeek
On Thu, Dec 27, 2018 at 09:39:56AM +0100, Otto Moerbeek wrote: > > Very little feedback so far. This diff can only give me valid feedback > if the coverage of systems and use cases is wide. If I do not get > more feedback, I have to base my decisions on my own testing, which > will benefit my sy

Re: Request for testing malloc and multi-threaded applications

2018-12-27 Thread Otto Moerbeek
Very little feedback so far. This diff can only give me valid feedback if the coverage of systems and use cases is wide. If I do not get more feedback, I have to base my decisions on my own testing, which will benefit my systems and use cases, but might harm yours. So, ladies and gentlemen, sta

Re: Request for testing malloc and multi-threaded applications

2018-12-19 Thread Otto Moerbeek
On Wed, Dec 19, 2018 at 10:52:03AM +0100, Otto Moerbeek wrote: > Hi, > > This diff implements a more flexible approach for the number of pools > malloc uses in the multi-threaded case. At the momemt I do not intend > to commit this as-is, I first need this to get some feedback on what > the prope

Request for testing malloc and multi-threaded applications

2018-12-19 Thread Otto Moerbeek
Hi, This diff implements a more flexible approach for the number of pools malloc uses in the multi-threaded case. At the momemt I do not intend to commit this as-is, I first need this to get some feedback on what the proper default should be. Currently the number of pools is fixed at 4. More pool