Opened 12 years ago
Closed 12 years ago
#142 closed defect (invalid)
petascope must not load metadata at startup
| Reported by: | Peter Baumann | Owned by: | Peter Baumann |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | petascope | Version: | |
| Keywords: | Cc: | Dimitar Misev, Piero Campalani | |
| Complexity: | Medium |
Description
petascope loads metadata into RAM at startup. This is bad from 2 perspectives:
- misses updates done in the db
- not scalable
requests must fetch metadata adhoc from the db, and release them afterwards (any kind of cache must remain transparent and not compromise concurrent work on the db).
Change History (2)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
…was a misunderstanding: not coverage metadata, but petascope system metadata.
Note:
See TracTickets
for help on using tickets.
As far as I know metadata for a coverage is read at every request, and released before returning the result or throwing an exception in case of an error. So this seems like an invalid ticket to me?