User Story #10178 (new)
Opened 11 years ago
Last modified 11 years ago
FS/Web stateful service interaction — at Initial Version
| Reported by: | jamoore | Owned by: | wmoore |
|---|---|---|---|
| Priority: | blocker | Milestone: | OMERO-4.5 |
| Component: | Web | Keywords: | n.a. |
| Cc: | web-team@…, fs@… | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
In 4.4, web methods were all converted to use a
svc = openStatefulService()
try:
svc.doWork();
finally:
svc.close()
idiom. In other words, no stateful service lives longer than a single web gateway method call. With Bio-Formats now backing many of the services (renderingengine, rawpixelsservice, etc), this means that each method call (getPlane(), renderJpeg()) is performing a full setIdinvocation. For some formats, this can take several seconds.
Melissa is working on reducing setId times, and eventually the Bio-Formats state can be cached server-side in order to further speed up the individual lookups, but there may still be the need for properly handling state from the web client.
A first step is likely to evaluate the user impact of the slow down (especially when several users are accessing the web simultaneously).
