John,
I've played with large files (reading) and 4D - and around 500 megs it starts
to get wonky.
I would:
use an SSD
create the (local) disk file (blob to doc with an empty blob.
repeat
build up your text to some size (100 megs?) then append it to the disk
file
until no more text
move file to network
should give you maximum stability
>
> I have been thinking along similar lines today. Just wondering if
> keeping 2.4 million rows in a text array in memory will be an issue.
> The text file is 831mb so if 4D can mange it that’s worth a try.
> Likely faster as one of the reports is taking 3-4 hours. And there
> are dozens of reports they need to run at the end of the month.
> That’s why it’s an overnight affair. (Although we could distribute
> the effort over several computers if we need to.)
------------
Hell is other people
Jean-Paul Sartre
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
