Loading data questions
Hi guys,
I have two questios on how to load data fast
1. If I have two html5 sites which contain the same amount of map layers, except there is only one map service in Site A, but there are a few map services in Site B, which site will load the data faster?
2. I have a layer which has many fields in the attribute table, I find it always takes long time to be loaded. If I delete all the fields from the attribute table, and put them in a related table. Will it be loaded faster?
Thank you
Feng
0
-
Not black and white. If you are trying to speed load time, then try to minimize what is called at open. I have a parcel file with a couple houndred thousand records and many fields, but I don't load this service at load time. Likewise, where are your layers stored? It is often faster to have them in File Geodatabase located on same box as ArcGIS Server. Sometimes if you need industrial indexes, then better to leave in SDE. Try in both to see what is faster. I personally keep my Address and Parcel files in SDE, since there are often searches and that take less time, but keep most others in FGDB. If you look at Statistics under Logs in ArcGIS Server, and then view Average Response for you services, you can see which is probably slowing your site open, and then work to make it faster. 0 -
Thank you Mike. Most of my layers are in SDE, I just don’t know if it will makes load time different when the site has one or multiple services. I will check the services respond time as you suggested for sure. Thank you. 0 -
Multiple services can load at the same time, so you would think more smaller services would load faster - but I've never tested it. If you are talking about services with too many layers (100?), then you should certainly break them up. A service with 20 layers compared to 4 with 5 each...I don't know. However, if you have a number of services, and one is slow, then the site will be slow to open. A site is as slow as its slowest service, basically. Find your slowest service, and fix it, then go on to the next. If a service is not needed until you zoom in, then set its min/max scale so it won't open at start. Separate those layers that are used by everyone from those used by just a few. Make sure that those services used by everyone are small and have the proper resources set in AGS. They need to be fast. Other Services that have layers that aren't used as much can be slower. 0 -
Yes I do have a service that has 100+ layers, maybe it’s better to break them up. Thank you for all suggestions, I will definitely test them. 0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
4 Kommentare