help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: textread function


From: Robert A. Macy
Subject: Re: textread function
Date: Thu, 22 Sep 2005 09:46:01 -0700

2.1.50 is very old, however, depending on whether you're on
WinXP or Win98 or ?

Here is a copy of email on how to expand memory.  It
provides the date we were talking about the subject for
further searches in the archives.

=-=-=-=
From: Richard Thomas
<address@hidden> 
Subject: Re: Possible to increase 256 Mb Memory Limit?
(Windows 2000) 
Date: Thu, 18 Nov 2004 10:27:10 +0000 
To: address@hidden 
 
I've finally managed to achieve increased memory (using the
combined Cygwin/Octave 2.1.42 p4atlas build under Windows
2000)! Hopefully this might help Robert too. The main
change was that Cygwin/Octave seems to be ignore the
"heap_chunk_in_mb" registry setting for the "local
machine", but does spot the one for the "current user".

In a Command Prompt (DOS) window, to set then check the
registry setting
"C:\Program Files\GNU Octave\bin\regtool" -i set
"/HKCU/Software/GNU Octave/Cygwin/heap_chunk_in_mb" 1216
"C:\Program Files\GNU Octave\bin\regtool" -v list
"/HKCU/Software/GNU Octave/Cygwin"

In theory, you should be able to set it for all users with:
"C:\Program Files\GNU Octave\bin\regtool" -i set
"/HKLM/Software/Cygnus\ Solutions/Cygwin/heap_chunk_in_mb"
1216

but this does not seem to get picked up by Octave. Also,
with my Windows2000 paging size set to 1536 Mb, if I try to
set the heap size to a larger value, Octave fails
immediately. Not sure why happens, but I've got rather more
memory to play with now so I'm happy:
"C:\Program Files\GNU Octave\bin\regtool" -i set
"/HKCU/Software/GNU Octave/Cygwin/heap_chunk_in_mb" 1300
"C:\Program Files\GNU Octave\bin\octave-2.1.4
2-p4atlas.exe"
C:\Program Files\GNU Octave\bin\octave-2.1.42-p4atlas.exe:
*** 2. unable to allo
cate heap, heap_chunk_size 1363148800, Win32 error 8

And if I set it above a certain size "regtool" fails with
the same error, so the registry has to be manually edited
with "regedit".

(calling "regtool" using "system" within Octave seems to
work OK as well, although as Marek points out you have to
be careful when file pathnames have space characters in
them).

Richard
=-=-=-=

Using this technique on the XP, I expanded the memory to be
large enough for the 20 MB files, something like
arbitrarily 1000MB and no longer had "segment faults" *and*
the program ran 10 times faster.

                    - Robert -

On Thu, 22 Sep 2005 08:18:45 -0500
 Shatat-Herres Moneer <address@hidden>
wrote:
>         hallo,
>  
>  I am just trying to read a very big txt file with octave
> using the function "textread". the txt file contains
> 94000 lines. each line contains 7 float variables. I am
> only able to read 10000 lines.
>  when I try to read more than 10000 lines from the txt
> file octave gives an error meassage "memory is
> exhausted".
>  may be you can help with this problem. do you know what
> could cause this problem ???. and how may I solve it. it
> is not OS specific I tried it on tow machines with
> different OS " windows XP and window 2K"
>  
>  I am using the last binary octave release 2.1.50 for
> windows. 
>  
>  thank you for your help in advanced 
>  moneer
>  
>  -- 
>       Dipl      
>
----------------------------------------------------------------------
> 
> Integrated Dynamics Engineering GmbH  
> Dipl. Ing. Moneer Shatat-Herres 
> Systems Engineering and Software Development 
> Karl-Liebknecht Strasse 30,  
> 65479 Raunheim   
> Germany 
> Phone: (+49)6142-940046 
> E-Mail: address@hidden 
>   http://www.ideworld.com 



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------



reply via email to

[Prev in Thread] Current Thread [Next in Thread]