Caching stops at 46.1%,

[JamalNUMAN]

Caching stops at 46.1%,

I???m wondering why caching stopped while the percentage completed is only 46.1%.

[ATTACH=CONFIG]24847[/ATTACH]

how about the rest?

Why the Caching is not in progress any longer?


Thank you


Best

Jamal

[JamalNUMAN]

There are a vast amount of variables here.

1st off, you say 'huge' I laugh, we have caches 10x that size even with small areas, mind you, we go down to 1:256 for some serious details.
Even with a tiny area, you are going down to the 1000 level so depending on the project area, size would be expected and by using Exploded method (which creates many folder directories as well as jpgs (though the advantage to this is 'merging' caches quite easily) the size problem is exaggerated.
Its again further exaggerated by using 128x128 tiles and again exaggerated using png without compression.

Try re-running the cache by selecting EXTENT of the map (after of course, getting the area you want) - I have had strange problems with using features as the area of interest (however, I think this was due to custom projections being used)

Use MIXED Tile format at 75 compression - you wont notice a difference!
Use 512x512 tile
Use Bundle format (compressed storage format)

as for the estimates shown, Ive yet to see one that is accurate or really close - its a big 'guess' done by samples and algorithms.

as for the 'caching never ends successful'
what does the geodatabase results show you? which failures, if any are in the attribute table?

Another thing you can do is create the service MANUALLY cache and send the GP request through Cache manager in Catalog to the map service when published.

Many thanks Michael for the �??road map�?� that you have provided in order to publish my mxd successfully with cache options,

I tried the settings that you have recommended but sound massive time is still required to get my mxd published with cache option.

[ATTACH=CONFIG]25854[/ATTACH], [ATTACH=CONFIG]25855[/ATTACH]

Till the moment I�??m writing this post, my published mxd is not completely cached. The total number of tiles at the scale of 1:1000 is 480635. Is that normal?

[ATTACH=CONFIG]25856[/ATTACH]

Best

Jamal

[MarcoBoeringa]

Therefore, all users are complaining due to the very slow speed in panning and zooming the maps accommodated in the web application.

Jamal,

I noticed one thing in your screenshots that concerns me. You have a lot of labels visible, and those labels seem to be dynamic. They are not a fixed size nor position.

Dynamic labeling is very costly in most cases, and you probably want to avoid this in your web services.

What you should consider, is converting your labels to Annotation Feature Classes in your geodatabase, probably best as a feature-linked version, that updates with updates to your parcels layer. As the Help page I linked says:

"Geodatabase annotation is indexed spatially, meaning that it will draw and select much faster."

You would also do good to set a fixed reference scale for the Annotation and labels, e.g. 1:5000, so as to have the labels scale. And set a visible scale range. As the Help says:

"To maximize ArcMap display and query performance, always define a visible scale range for each annotation class so annotation features only draw when you're zoomed in enough to read their text."

[JamalNUMAN]

Jamal,

I noticed one thing in your screenshots that concerns me. You have a lot of labels visible, and those labels seem to be dynamic. They are not a fixed size nor position.

Dynamic labeling is very costly in most cases, and you probably want to avoid this in your web services.

What you should consider, is converting your labels to Annotation Feature Classes in your geodatabase, probably best as a feature-linked version, that updates with updates to your parcels layer. As the Help page I linked says:

"Geodatabase annotation is indexed spatially, meaning that it will draw and select much faster."

You would also do good to set a fixed reference scale for the Annotation and labels, e.g. 1:5000, so as to have the labels scale. And set a visible scale range. As the Help says:

"To maximize ArcMap display and query performance, always define a visible scale range for each annotation class so annotation features only draw when you're zoomed in enough to read their text."

Many thanks Marco for the help,

The issue here is that even in case of publishing an mxd of simple feature class with no labels, the cache is not completed

Scenario:

Consider an mxd file that contains only one feature class (attached) with the following properties

1. No labels
2. The surface area is 131x51 km
3. The data size is about 800 kB

[ATTACH=CONFIG]25932[/ATTACH], [ATTACH=CONFIG]25933[/ATTACH]

Caching this mxd is never completed with the settings below

[ATTACH=CONFIG]25934[/ATTACH], [ATTACH=CONFIG]25935[/ATTACH]


Challenges:
1. Publishing data introduces slow speed when the services are accessed by web applications or even with the arcgis desktop! Services are quite slow when accessed anyway

2. Caching the service is either not completed or takes long times (hours) even for very light data. Then caching is almost impossible anyway.



Then what is the benefit of publishing data while the performance (speed) is slow?