|
|
|
|
|
by masklinn
3542 days ago
|
|
> If you're doing your own custom parsing you can write your own numeric parsers to remove support for parsing nan, inf, -inf, etc and drop scientific notation which will claw back a lot of the time. The 200MB/s, at least for rust-csv, is for "raw" parsing (handling CSV itself) not field parsing and conversions, so those would be additional costs. > If you also know the exact width of the date field then you can also shave plenty of time parsing datetimes. Yes if you can have fixed-size fields and remove things like escaping and quoting and the like things get much faster. |
|