delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1998/09/09/16:25:16

From: tolj AT uni-duesseldorf DOT de (Stipe Tolj)
Subject: Re: calloc() more then 140MB under cygwin b19.1?
9 Sep 1998 16:25:16 -0700 :
Message-ID: <35F5B4AA.357EC49.cygnus.gnu-win32@uni-duesseldorf.de>
References: <009CBE5F DOT 6DB96720 DOT 15728 AT ifk20 DOT mach DOT uni-karlsruhe DOT de>
Mime-Version: 1.0
To: dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Cc: gnu-win32 AT cygnus DOT com

> I finally was forced to test cygwin b19.1, because my prog runs for hours
> under Interix (formerly OpenNT), whereas it's extremely fast under Linux,
> using about 300 out of 512MB RAM.
>
> Under b19.1, I get NULL from calloc() after only about 140MB.
> Isn't HEAP_CHUNK_SIZE eliminated? At least I got no such messages...
>
> BTW, while I'm typing this, I'm also testing UWIN 1.51 with egcs.
> It's not yet finished and took already seven times the CPU of Linux!
> Could it be a general NT4.0SP3 alloc/free performance problem?

So, if your are working on that big memory allocs I would consider to use
Linux anyway.

But try at least b19.2 patch from Sergey at http://www.lexu.ru/sos.

Regards, Stipe.


--
Stipe Tolj <tolj AT uni-duesseldorf DOT de>
Cygwin32 Porting Project
Department of Economical Computer Science
University of Cologne, Germany
http://www-public.rz.uni-duesseldorf.de/~tolj



-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019