Select to view content in your preferred language

Parcel Editor seems slow

5967
21
08-16-2010 08:30 AM
MarkVolz
Frequent Contributor
I have noticed that Arc 10x seems pretty slow compared to 9.x.  I have noticed that the new parcel editor seems particularly slow.  I will often wait about 15 seconds before I am allowed to edit a parcel.

My machine is rather new - core 2, 4 GB ram, decent graphics card.  Does anyone have any thoughts as to how I can speed the system up?
Tags (2)
0 Kudos
21 Replies
DianeRodrigues
Emerging Contributor
I don't get that option when I follow your instructions.  Is that available for ArcMap 10 Geodatabase?

How many parcels do you have in your parcel fabric?

I have found that recalculating indexes on the parcels, lines, points and linepoints tables after migration really helps with speeding things up.

To recalculate indexes on the parcel fabric feature classes, right-click the fabric in ArcCatalog or the Catalog window and click Properties to open up the Parcel Fabric Properties dialog box. Click the Fabric Classes tab and select the feature class in the drop-down for which you want to recalculate indexes and click properties.

Click Recalculate to recalculate the indexes for the fabric feature class.

Christine
0 Kudos
ChrisBuscaglia
Esri Contributor
Yes, the option to recalculate spatial indexes exists for a version 10 GDB.  You'll have to navigate to the Parcels and Lines classes of the Parcel Fabric via the Parcel Fabric property page.  I've included a screenshot above, please let me know if you have any other questions.

Here is a generic link to how calculating spatial indexes optimizes datasets.

http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//001700000060000000.htm


Chris

Parcel Editing Team
0 Kudos
DianeRodrigues
Emerging Contributor
I don't seem to have that option to "recalculate indexes".  I can add or delete an index. . . I'm using a personal geodatabase as my database
0 Kudos
DianeRodrigues
Emerging Contributor
Today the speed has become even slower (I didn't think that was possible).  I'm not sure why.  Originally I thought my older PC was the problem causing my Parcel Fabric to crawl but it's doing it on my new machine as well (Win7 64bit 8GB RAM i5 @ 3.3ghz RADEON HD 6450 1GB)

Does the parcel fabric size cause the problem?  My fabric holds about 85,000 parcels, 250,000 points, 550,000 lines.  Any other recommendations besides reindexing which I can't seem to do since it doesn't provide that option?
0 Kudos
MarkVolz
Frequent Contributor
FYI:

1)  Someone mentioned to me that moving the parcel fabric to a local drive, instead of on the network made the parcel editor faster.  That seems to have helped out.

2)  Another issue I had with my application is that ArcGIS seemed crash prone.  ESRI support mentioned if that I should clear C:\Users\user\AppData\Roaming\ESRI\Local Caches.  It seems to have helped.
0 Kudos
DianeRodrigues
Emerging Contributor
Thanks for the recommendation unfortunately it didn't solve my problem.  It sadly made it worse which was a surprise.  I did run a parcel fabric check and have a few errors.  maybe I just have one bad parcel goofing up the whole lot.  I think I'll work on fixing that until I hear how to reindex.
0 Kudos
MarkVolz
Frequent Contributor
Not being an expert, here are a couple things I would try:

*use the mxd defrager.
*open a new mxd and bring only the parcel fabric in.  If you notice a speed difference then your issue is with the mxd  (which can be replaced)
0 Kudos
DianeRodrigues
Emerging Contributor
Darn those ideas didn't work either.  How I wish it was an easy solution!  Oh well I have time to work on it again today. I think I'll just focus on cleaning up Fabric Errors from the original import.  Who knows if I get lucky maybe once they are all cleaned out I'll see an increase in speed.

Thanks for trying though Mark.  I have found MXD's causing problems in the past it would have been nice if it was the same for this problem.
0 Kudos
CarlosIsaac_Cabrera
Deactivated User
Darn those ideas didn't work either.  How I wish it was an easy solution!  Oh well I have time to work on it again today. I think I'll just focus on cleaning up Fabric Errors from the original import.  Who knows if I get lucky maybe once they are all cleaned out I'll see an increase in speed.

Thanks for trying though Mark.  I have found MXD's causing problems in the past it would have been nice if it was the same for this problem.


We've had slow editing for a while.  I'm sure ESRI knows this is an issue.
0 Kudos
DianeRodrigues
Emerging Contributor
Okay folks I found the solution for me. 

Do not use a personal Geodatabase.  Use as File Geodatabse.  File Geodatabase allows you to reindex unlike the Personal Geodatabase.  Now I just need to figure out how the heck I move over my data . . . ESRI REALLY needs to release a book on how to properly use these tools.  Some of us can't go to training 😞
0 Kudos