Opened 16 years ago
Closed 16 years ago
#129 closed enhancement (fixed)
LoadMap performace issues
Reported by: | assefa | Owned by: | assefa |
---|---|---|---|
Priority: | P2 | Milestone: | 2.0 |
Component: | Widgets | Version: | 1.0.7 |
Severity: | Major | Keywords: | |
Cc: | pagameba | Browser: | All |
External ID: | Operating System: | All | |
state: | New |
Description
It was reported that performance was very poor when using Fusion Mapguide with Oracle DB. This bug is to track any enhancements that need to be done to address this.
Change History (4)
comment:1 by , 16 years ago
Status: | new → assigned |
---|
comment:2 by , 16 years ago
comment:3 by , 16 years ago
Cc: | added |
---|
The first set of optimization had a significant impact on the time of the load map with oracle data (which was the initial goal). Here are some numbers, part of an e-mail:
" I did more tests with the current svn version of fusion. The map file contains about 15 oracle layers (most of them are tables that are exactly the same: with about 1000 records and 15 attributes):
- The LoadMap time before the change was about 39seconds
- the LaodMap time after the changes is about 4 seconds
I could not really replicate the level of slowness described by Tom "They had a map with 162 layers taking more than 30 minutes to load in the Fusion viewer. Even a map with 10 layers took 7 minutes.",
but I assume the more you add layers the more time the load map would take (for example adding an additional 10 layers in the my test map bumped the loadmap time from 39s to 73s) "
I will leave this bug open for some time until we get a better oracle test data or if there are other issues.
comment:4 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
implemented; open a new ticket to report any issues
first commit done in r1541: cleanup of LoadMap.php