eclipse-ee4j / eclipse-ee4j/jersey
Document performance penality introduced by DataSource Provider
Open
Component: docs
Component: performance
Priority: Major
Type: Task
- Dominant language
- Java
- Stars
- 730
- Forks
- 382
- PR merge metrics
- No merged PRs in 30d
Description
Document that the DataSource implementation used by Jersey is backed by a byte array. That might introduce a huge performance/memory penality when huge data is processed.
In my case, a client can upstream large files (hundreds of megabytes), I requested Jersey to provide a DataSource. Memory exploded. I resorted to an inputStream with a custom InputStreamDataSource in the backend. That sovled the issue.
#### Affected Versions
[2.16]
Contributor guide
Assessment
This issue has not been assessed yet.