File size limits

[Gustav]

Hello!

Did someone know the file size limits of these extensions?

Binary (+ Quickload) - e.g. for zipping files
Named Variable
Blowfish


Thanks in advance
Gustav

[Jeff]

How big have you done so far?
As far as I know no one has reported a limit so it may be an OS file size limit.

[Gustav]

I want to know the limits before it's too late and for the user documentation, because the database I use in my current program could be very huge (1 GB). I don't want to split it if possible.

I'm not sure especially about the Binary object.

[SEELE]

why don't you test it and find out?

[Gustav]

This could be funny.
But before I'm trying to do something stupid, I want to ask here...

The Binary object is a little bit suspect for me... :eek:

[Dynasoft]

If the object loads a file entirely into memory (or makes an entire file memory-accessible, i.e. Binary Quickload), the limit is about 1.5GB, possibly much lower depending on virtual memory fragmentation. Though most people don't have this much ram anyway. It's not a good idea to use more than 100MB of ram if you want to run on common PCs.

If the object only processes a file, loading a small amount at a time, then the size of the file is only limited by the filesystem (2GB for FAT32, MUCH larger for NTFS).

I don't know how each of them work, but I suspect they all use the first one.

[Gustav]

Thank you very much for your answer.
This should be enough...

And with the Binary Quickload I can handle errors (e.g. if not enough RAM), that the Binary not supports in this way.

[Werbad]

4gb for Fat 32...

[Dynasoft]

4gb for Fat 32...

Indeed, I was wrong there. Though it's worth noting that some programs (and most likely MMF extensions) puke on files over 2GB because they mistakenly use signed numbers for filesize.