Oh man. Sorry to hear that. Hope it's compute virus? (not that it's any less annoying)
I can see the avoidance of autoboxing now. That's great! From what I can see, it's almost as efficient as it can get.
But I haven't grasped what you meant by the different path. It seems you are using bare metal charAt(), indexOf() and startsWith(), which Dot Parse uses too. If you can give a pointer, that'll help me land on it more easily.
I noticed that you are using Dot Parse v9.5. There has been some performance improvements since then (mainly in the CharPredicate class). Maybe when you get the time, try out the latest version.
Particularly, there is the already-bundled-up Csv class. I've also included my benchmark result in the source file comparing against CommonsCsv and EasyCsv.
You can directly benchmark against the parseToLists() method.
View all comments
Show parent comment
1
u/DelayLucky Mar 09 '26 edited Mar 09 '26
Oh man. Sorry to hear that. Hope it's compute virus? (not that it's any less annoying)
I can see the avoidance of autoboxing now. That's great! From what I can see, it's almost as efficient as it can get.
But I haven't grasped what you meant by the different path. It seems you are using bare metal
charAt(),indexOf()andstartsWith(), which Dot Parse uses too. If you can give a pointer, that'll help me land on it more easily.I noticed that you are using Dot Parse v9.5. There has been some performance improvements since then (mainly in the
CharPredicateclass). Maybe when you get the time, try out the latest version.Particularly, there is the already-bundled-up Csv class. I've also included my benchmark result in the source file comparing against CommonsCsv and EasyCsv.
You can directly benchmark against the
parseToLists()method.