Hi Runar Annoying isn't it? Try this for a test. Open up a filter, then go to View...By Form and select another form that your filter isn't attached to. Then try modifying and saving the open filter - on my system it is nearly instantaneous.
Then change the objects you are viewing - click on Forms, then click back on Filters, and try it again. First time takes a long time, then instant again after that. It looks to me as though it is caused by the admin tool refreshing the list of objects displayed in the admin tool. If it knows the object isn't in the list it is currently displaying, there is no delay... otherwise it can take some time. I don't know whether this throws any light on the issue or not... David Sanders Remedy Solution Architect Enterprise Service Suite @ Work ========================== ARS List Award Winner 2005 Best 3rd party Remedy Application tel +44 1494 468980 mobile +44 7710 377761 email [EMAIL PROTECTED] web http://www.westoverconsulting.co.uk -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Runar Helle Sent: Wednesday, November 22, 2006 3:18 PM To: arslist@ARSLIST.ORG Subject: Administrator - Performance Issues when saving form Hi, all I've got a question about performance in AR Administrator. The performance varies for each time I save. Sometimes it takes up to 25 seconds to save a filter, other times only half a second. We are talking about the same filter, and the change could be as small as changing a character to its name (add or remove. Makes no difference) The interesting thing is that it seems to be very slow the first time I save the filter. If I make an other change, save is quick. And if I make yet an other change it is also very quick. If I then turn to the user tool and do *any* operation that does an API/SQL call to the server, it all breaks down again. The first time I save anything in the admin tool after touching the user tool, things are sloooooow. After the first save operation in the admin tool, subsequent saves to that element is quick again..... Good thing: It's consistent. I've have checked the API&SQL log and the difference in API-time between the "quick" and the "slow" saves is only milliseconds. CPU usage on server is only 50 percent at its peak during save operation. For the quick saves, I can hardly register any CPU load on the server. There is no noticeable load on the client either. The server is a dual 3.4 GHz with 3,5 GB RAM. Administrator 6,3 patch 12 ARS 6.3, patch 12 Any ideas? Best regards, Runar ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"