Skip to content

Commit 0c598c5

Browse files
committed
Docs update
1 parent 2294533 commit 0c598c5

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed
-14.6 KB
Loading

docs/limitations/csv_file_size.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,11 +55,11 @@ The above experimental results make smooth to arrive to the following conclusion
5555
* VBA-CSV interface is suitable to almost any Microsoft Office Excel user. It can handle considerably large CSV files without any problem.
5656
* As the size of the CSV increases, VBA-CSV interface has a performance drop.
5757
* With each available GB of RAM, on the test machine, VBA-CSV interface can parse CSV files sized up to 107.61 MB.
58-
* VBA-CSV interface can work at high performance with files sized to almost \[75.45 * Available RAM\] (results in MB).
58+
* VBA-CSV interface is supposed to work at high performance with files sized to almost \[75.45 * Available RAM\] (results in MB).
5959

6060
>⚠️**Caution**
6161
>{: .text-grey-lt-000 .bg-green-000 }
6262
>The formulation presented here is experimental and can be wrong due the assumptions involved. There is a real chance to experiment unexpected behavior. User need to remember that parse a 2 GB sized CSV file can require up to 20 GB of Available RAM.
6363
>
64-
>The target CSV can't have size greater than 2GB. This because VBA-CSV interface use `LONG` datatype when parsing. So, if you want to process files larger than 2GB, you'll need to use another solution instead.
64+
>In theory, the target CSV can't have size greater than 2GB but in practice this value can be 1.5 GB. This because VBA-CSV interface use `LONG` datatype when parsing and due the VBA language is not really good when manages RAM.. So, if you want to process files larger than 1.5GB, you'll need to use another solution instead.
6565
{: .text-grey-dk-300 .bg-yellow-000 }

0 commit comments

Comments
 (0)