This topic is locked

Very slow add/edit

5/24/2016 8:46:34 AM
ASPRunner.NET General questions
Pete K author

I have a table that has six fields (Organizer, Approver, Presenter, etc.) that all relate to a Users table. Each has a drop-down list. When I was testing my app as I developed it, everything worked great. At that time I had about a dozen test users in the users table. Now that I am preparing for a beta test, I have populated the users table with around 6,000 real users. Now it takes up to 45 seconds to commit any changes to the main table (add or edit). When editing directly in SQL Studio, the add/update operations are instantaneous.
The weird part is that I was concerned about this from the beginning, but I though the issue would be initially populating the drop-downs and using them. But there is no performance lag there. It's only when saving changes that the app drags.
Any ideas on how I might improve the performance?

Sergey Kornilov admin 5/24/2016

Need to see your project in action to see what exactly causes the delay. There is definitely something else happening besides the update itself.

Pete K author 5/24/2016



Need to see your project in action to see what exactly causes the delay. There is definitely something else happening besides the update itself.


Thank you Sergey. I might be onto a solution. I'll keep you posted and if I need more help I'll submit a ticket. Appreciate the quick reply.

Sergey Kornilov admin 5/24/2016

Sure, keep me posted. Sounds like an interesting problem to solve.

Pete K author 5/26/2016

[size="2"]So, one thing I left out of my OP was that my table wasn't normal form. I had four Presenter fields: Presenter1, Presenter2, etc. in addition to the Approver and Organizer fields. So every time a record was being accessed in the main table, it was pulling in 6 instances of the User table, which itself contains over 6,000 records. [/size]
When I was experimenting around with settings I discovered that I could use a multi-select Javascript control to populate one field with a comma-delimited list of values. I wound up consolidating my four presenter fields into just one and making a multi-select. That presented some display issues -- ASPR apparently doesn't look up the names for values stored this way but displays the raw UserIDs, so I wrote a method to do that. Now that that's all done, performance has increased a great deal. It's still a tad slow, but nowhere near as bad as it was. And using the one multi-select field of course has the added advantage of allowing as many selections as the field size allows, and I thing the JS user control is very user-friendly.