Task #11184 (new)
Opened 11 years ago
Last modified 11 years ago
Unexplained import overhead — at Version 1
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | critical | Milestone: | OMERO-5 |
| Component: | OmeroFs | Version: | 4.4.8 |
| Keywords: | n.a. | Cc: | fs@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | FS demo 4.x |
Description (last modified by jamoore)
While preparing the FS workshop for Paris, there were a few surprisingly slow imports. An LEI dataset for example took roughly 100 seconds for some 140 files, while the pixel upload was much slower. Watching the stack traces via jstack in at least one instance, pointed at some of the directory creation logic to be taking too long. Perhaps due to one transaction per file?
This code path needs to be optimized. Though it's usable, there's no reason any of the OME5 imports should be significantly slower than the OME4 imports, unless there's significant non-binary data contained in the files.
Change History (1)
comment:1 Changed 11 years ago by jamoore
- Description modified (diff)
- Version set to 4.4.8
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
