Tell me more ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.
up vote 2 down vote favorite

Is anyone using the ESRI JS-API having issues over the last week or two with either latency or performance in the client download and operation? Since about 7/12/2011 we have seen across numerous ISPs and Browser/OS platforms in WA state issues with users getting the application to load and operate normally.

The only workaround I have had is to switch my app to using the compact api, to reduce the download footprint.

share|improve this question
Another possible workaround would be to download the API, put it on your server, and reference all of your app's to the local API. It's not always feasible, but it will save the hops to/from Esri's servers if you have the bandwidth and server resources. – GeoKevin Jul 20 '11 at 18:47
Kevin; yes that is one option I am considering; but these are blade-servers which have a smaller back-plane so there are concerns with throughput from my network folks but I am looking at that as a option too. – D.E.Wright Jul 20 '11 at 18:54
They have a pretty aggressive cache expiration of a year, that said, I disable caching and it's taken around 3-10 seconds a few times lately. Today though its half a second. Only way to remove that unknown is to host it yourself and see if you get better performance. – Steve Jul 20 '11 at 19:26
1  
This question may be somewhat related to GIS (although it probably fits better on sites about servers), but according to our FAQ it's too localized (in time) to be of lasting value on this site. – whuber♦ Jul 20 '11 at 21:59

closed as too localized by whuber♦ Jul 20 '11 at 22:00

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.