The problem in this particular case is that Fusion unnecessarily
enumerates the full schema of all the layers during initialization,
which for the Oracle provider in particular is very slow. The ajax
viewer takes a different approach and defers schema enumeration until
it is necessary for
Nope - not using Oracle for anything (though I am using Access to
render spatial objects)...Just a suggestion from someone who was also
noticing a slow Fusion startup time, compared to ajax.
Andrew
gingerbbm wrote:
We're using IIS6. Are you using Fusion to render Oracle spatial objects i
We're using IIS6. Are you using Fusion to render Oracle spatial objects in
MapGuide?
I'll take a look at that link!
--
View this message in context:
http://www.nabble.com/Fusion-%2B-Oracle-datasource-problem-tp17884373p19092627.html
Sent from the MapGuide Users mailing list archive at Nabble.co
What sort of webserver are you running? I'm using IIS5, and just
enabled compression using FlatCompression (www.flatcompression.org) and
it has dramatically sped up my initial load times for Fusion
Andrew
gingerbbm wrote:
Rock Beans wrote:
To be honest how does the data sou
Thanks Paul :)
--
View this message in context:
http://www.nabble.com/Fusion-%2B-Oracle-datasource-problem-tp17884373p19092411.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
mapguide-users mailing list
mapguide-users@lists.o
Rock Beans wrote:
>
> To be honest how does the data source type affect one viewer over the
> other
>
It's simply the problem that startup takes an age - if it works at all. And
with more than ten or so layers it simply doesn't work. But it's true that
if and when the initial load is done it al
To be honest how does the data source type affect one viewer over the
other. I would think you would have the same issues in both. Most of
the API calls are identical. I know there is a JavaScript compression
fix that should be released soon with Fusion that should speed up
initial loads. I am seei
We also discuss things on the fusion mailing list (see http://trac.osgeo.org/fusion)
.
Please note that there is typically a long lag between new open source
development and the appearance of the code in related commercial
products as the commercial products typically go through much longer
That all sounds really promising but unfortunately I'm working to an
aggressive deadline, and having paid money for the Autodesk MapGuide product
I sort of assumed it would operate consistently regardless of my choice of
viewer.
So what's the best way of keeping track of these new developments? D
We are going to be looking specifically at this issue of startup time
in the next few weeks, it would be very useful to be able to have you
test and provide feedback on how much improvement we are able to make.
The current method of initialization enumerates the full schema of all
the layer
I'm pretty disappointed. I've invested a lot of time learning Fusion and now
I discover that as far as Oracle is concerned it's not fit for purpose. It
takes an age on initial load, and has a limit of around ten layers maximum.
:(
--
View this message in context:
http://www.nabble.com/Fusion-%
this will make a huge diference
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc53
does fusion make it's requests in a sync or aync fashion? if they aren't sync,
there maybe one or more full describe schemas being performed
z
On Wed, Aug 20, 2008 at 10:09 PM, gingerbbm <[EMAIL PROTECTED]> wrote:
I wish I hadn't just discovered this issue.
Paul Spencer-5 wrote:
>
> I hope that this will be part of the next Fusion release.
>
Is Oracle + Fusion speed going to be improved in the next release? And when
is the next release?
--
View this message in context:
http://www.nabble.com/Fusion-
Hi Klaus,
this is something that others have reported to me as well, it seems
that Fusion does some dumb things on initialization that it doesn't
really need to do, including retrieving the schema of layers in the
MapDefinition. Fixing this will require some rearchitecting of how
Fusion
Hi
The problem is that the Fusion Viewer loads very slowly compared to AJAX and
DWF viewers when using Oracle database as a feature source. The AJAX and DWF
viewers load to browser in about two seconds, but the Fusion Viewer takes
tens of seconds and with some maps times out after a minute. The l
15 matches
Mail list logo
