[Octave-bug-tracker] [bug #50619] textscan weird behaviour when reading a csv

[Philip Nienhuis]

Follow-up Comment #6, bug #50619 (project octave):

100,000's of lines is no big deal. 10e5 * 100 chars/line ~ 10 MB, that's still
fairly tiny considering that char arrays can be 2 GB (with 64-bit Octave).
As soon as you hit 1 GB (a factor of 100 away) you should become a little wary
as data are copied over internally into potentially much larger data objects.
But do use 64-bit Octave.

Chances are that textscan() won't be fixed very soon. So you need a
workaround.
I'd advise trying with dlmread, csvread or csv2cell anyway; in top (*nix) or
Task Manager (Windows) you can follow how much memory is consumed. You can
read big datafiles in big chunks at a time.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?50619>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/