Performance Question
- Dominant language
- C#
- Stars
- 490
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
I'm curious about general performance benchmarks for this library. I have a 25 MB file that takes 11 minutes to parse. It seems like it should be faster. As a test I serialized the same data into JSON then deserialized again. The JSON serialization took 4.1 seconds. The JSON deserialization took 5.9 seconds to the same objects with the same data. Is it realistic to compare JSON deserialization to EDI deserialization?
Does anyone else have information on what is considered good time for processing EDI files?
Is there something I need to tweak with this library to get better performance? Is there any general guidance for the models on how to improve performance? Could improper attribute usage cause performance problems?
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is named. Start by locating the EDI parsing and deserialization path, then reproduce the reported 25 MB file case and compare its timing with the stated JSON results; done means documented benchmark findings and any confirmed performance guidance or actionable bottleneck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100