#291 closed enhancement (fixed)
SECORE performance improvement
| Reported by: | Dimitar Misev | Owned by: | mrusu |
|---|---|---|---|
| Priority: | major | Milestone: | 8.4.2 |
| Component: | secore | Version: | 8.3 |
| Keywords: | Cc: | Piero Campalani | |
| Complexity: | Medium |
Description
SECORE has not been optimized for performance at all and hence it's pretty slow.
The operation that has most impact on performance is the flattening of GML definitions, so we should try to optimize this with some smart caching or proper indexing and XQuery use in BaseX.
Change History (3)
comment:1 by , 12 years ago
| Complexity: | → Medium |
|---|
comment:2 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:3 by , 11 years ago
| Milestone: | 9.0 → 8.4.2 |
|---|
Note:
See TracTickets
for help on using tickets.
Submitted patch introducing caching; only the first retrieval is slow (1s typically), afterwards it's mighty fast