Opened 15 years ago
Closed 15 years ago
#811 closed defect (fixed)
Maestro breaks down on a significantly large amount of resources.
| Reported by: | jng | Owned by: | ksgeograf |
|---|---|---|---|
| Priority: | medium | Milestone: | Maestro-2.0 |
| Component: | Maestro | Version: | |
| Severity: | major | Keywords: | |
| Cc: | External ID: |
Description
We have a very large MapGuide dataset that is causing Maestro to break down with OutOfMemoryExceptions.
Maestro currently loads the entire resource tree on startup. While this is fine for your average sized dataset, on the extremely large side of things. This is very ineffective.
Maestro should either utilise the new EnumerateResources API (if supported by the server) or only partially load the resource tree.
Change History (3)
comment:1 by , 15 years ago
| Status: | new → assigned |
|---|---|
| Version: | 2.0.1 |
comment:2 by , 15 years ago
| Milestone: | → Maestro-2.0 |
|---|
comment:3 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Fixed in r3836.
I have used the new API to avoid loading subfolders. This has the drawback that all folders will appear to have content, but may be empty after expanding the node. I can live with this minor defect, so I consider the issue fixed, feel free to re-open if you disagree.