Re: [Octave] Improving Octave for large files

[David Bateman]

Christian Brædstrup wrote:
> Okay, I didn't know the feature request was that old.
> When the code is so untested then perhaps the best thing to do is to create
> some large files and see how Octave handes them to begin with.
>
>   
The more people using 64-bit versions of Octave the faster the bugs will 
be worked out.. It takes a bit of effort to get a 64-bit build of Octave 
right though as the integer type for blas, lapack and other libraries 
needs to be 64-bit, though it can be done...


> As far as I have been told TPIE sorts all the data from the input file and
> then only access the data it needs after the sort (to save memory space).
> The reason I suggested the library is because I know it is actively
> developed at a university level and that the group uses it to handle very
> very large sets of satelite data to do 3D terrain mapping. But if using the
> library involves rewriting a lot of good code it would be foolish to use it.
>
>   
As I said I don't know TPIE but it sounds like one solution to its 
integration might be find a way to allow Array<T>::data to be replaced 
with an external representation given by TPIE, though doing that might 
be quite dangerous

D.


--
David Bateman                                address@hidden
35 rue Gambetta                              +33 1 46 04 02 18 (Home)
92100 Boulogne-Billancourt FRANCE            +33 6 72 01 06 33 (Mob)