Description
The parser is currently a real memory burner. I fed it a 4MB CSV file and ran the TPTP profiler. As you can see the parser creates around 100MB of garbage whereas it could (in really optimized) use around 4MBs. Such figures are not acceptable within a server environment. Please attach insights and patches to this issue report.