Skip to content

Partial I/O when reading file from HTTP (S3) #284

@grzanka

Description

@grzanka

I was thinking of employing JSROOT as "online browser" of some large (>1GB) ntuples. I was planning to store the ntuples under publicly available HTTP address, on S3 storage (with CORS properly configured). The JSROOT could be part of static JS+HTML app served on GitHub pages.

Main aim would be to use "Open with player" option for ntuple. User could type the column names to plot, and possibly define cuts, like on example below:
Screenshot 2024-02-07 at 14 08 07

I was curious how does I/O works when dealing with large ntuples. When I open the ntuple as URL what is being downloaded to my local browser session ? Only the columns which I select or whole file ?

I saw here:
#169 (comment)
that you mentioned partial file access.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions