Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Records loading is very slow if several MB of elements are present. #17

Closed
evilsocket opened this issue Dec 4, 2017 · 0 comments
Closed

Comments

@evilsocket
Copy link
Owner

evilsocket commented Dec 4, 2017

Record model should be changed to have a DataSize additional field. The /api/storage/1/records should not return the Data field, instead the data should be requested and streamed from a new route type, specialized on data streaming:

/api/storage/1/record/2/data

Until the data xfer is not handled like ths, the application will be always limited in the number and size of records it can loads on a list (since every record contains all its data), that is why uploading files that are too big and/or too many is discouraged until this issue is marked as fixed.

@evilsocket evilsocket self-assigned this Dec 4, 2017
@evilsocket evilsocket changed the title File lazy buffering. Record data streaming. Dec 4, 2017
@evilsocket evilsocket removed their assignment Dec 4, 2017
@evilsocket evilsocket added this to the 1.0.0 milestone Dec 4, 2017
@evilsocket evilsocket self-assigned this Dec 5, 2017
@evilsocket evilsocket changed the title Record data streaming. Implement record data streaming on a specialized route. Dec 7, 2017
@evilsocket evilsocket changed the title Implement record data streaming on a specialized route. Records loading is very slow if several MB of elements are present. Dec 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant