Long Load Times with new SFV vs old version

[JayGeisen]

Is it just me, or does the new (v2.2) SFV take much longer to load than the old one (v1.x) did?  Is there anything that can be done about this?

Thanks

[JayGeisen]

Just thought I'd bump this before resigning myself to ten second load times.

[RobertScheitlin__GISP]

Jay,

   Are you using esri basemaps? It could be that map services are having to be reprojected to WKID 102100 now in your viewer.

[JayGeisen]

Hey Robert,

No ESRI basemaps here.  I'm using the same services I use in our current (old) app.  The difference is something like double the amount of time new vs old. 

Jay

[RobertScheitlin__GISP]

Jay,

   Hmm... I got to say I haven't seen this.

[JayGeisen]

I tried changing the number of widgets and the number of widgets that load as open, but neither of those seem to make much of a difference.  What variables can you think of that would affect load time?

[RobertScheitlin__GISP]

Jay,

   All I can do is advise what I would do. I would begin with stripping out any widget or other from the main config.xml that I could. Next I would test with one basemap and no other layers at all and see if the responsiveness improves.

[JayGeisen]

Thanks, Robert.  I will give this a try and post back if I figure it out.

[AlexJones]

Jay,

Have you tried the out of the box viewer on your server? I am interested to see if the standard application is also slow to load in your env. On the same path are your widgets standard or customized? Same server? It might help narrow down if its services, server, custom code, etc. This would be in addition to Roberts idea of cutting it down to the core and building it back up.

[JayGeisen]

I will give that a try, thanks.