User Story #1035 (new)
Opened 16 years ago
Last modified 15 years ago
Provide buffer-proxy interface arguments for blitz clients
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | Bin-Services | Keywords: | performance, ice |
| Cc: | dzmacdonald, jburel, cxallan, cblackburn, carlos, atarkowska, bwzloranger | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Once insight and importer switch to using blitz, it may make significant sense to offer parallel methods to take and return ByteBuffer, IntBuffer, ... proxies which could be passed all the way to/from OmeroFs or any other store (e.g. for historgrams or projections).
Another alternative would be to have clients pass in ByteBufferCallBacks, so that the server handles the for-loop.
Whatever metaphor we implement, passing proxies from as close to the source of binary data to as close to the consumers as possible will increase performance.
Change History (2)
comment:1 Changed 15 years ago by jmoore
- Milestone changed from OMERO-Beta4 to OMERO-Beta4.1
comment:2 Changed 15 years ago by jmoore
- Milestone changed from OMERO-Beta4.1 to Future
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
We can look at this more with the server-side import changes for 4.1