How's xhtml editing performance for you?

User interface engineers at work are running into ugly performance problems editing xhtml files although personally I'm not. Admittedly, since I focus on the back-end I'll go into an xhtml file only touching a line or two while the UIE's dive in and tear up xhtml files with heavy editing cutting out and moving whole sections. Our setups are identical (6.0.4) and I've checked their logs for any obvious problems and found nothing. Idea becomes semi-responsive and unresponsive at times for them, but I can do those small edits even while analysis is happening and everything is fine.

What are you seeing on xhtml editing, particularly heavy editing? Any pointers?

1 comment
Comment actions Permalink

Jon Steelman wrote:

User interface engineers at work are running into ugly performance problems editing xhtml files although personally I'm not. Admittedly, since I focus on the back-end I'll go into an xhtml file only touching a line or two while the UIE's dive in and tear up xhtml files with heavy editing cutting out and moving whole sections. Our setups are identical (6.0.4) and I've checked their logs for any obvious problems and found nothing. Idea becomes semi-responsive and unresponsive at times for them, but I can do those small edits even while analysis is happening and everything is fine.

What are you seeing on xhtml editing, particularly heavy editing? Any pointers?


As always, CPU snapshots are probably the only way to nail things down.

Max

0

Please sign in to leave a comment.