Hi Xavier,

This seems to be a very interesting issue to troubleshoot , but without actually seeing the stack trace it might be difficult. 

Couple of suggestions if you can try just to see where the issue could be or better if the impact of the problem could be reduced by using some alternate methods.

1) Did you check in Chrome browser if the speed is okay? I know it may sound odd but for some reason (if we just choose to ignore the actual data fetch from SQL) the JS is sometimes (most of the times) much faster on chrome. Could you please check if there is at least little improvement on your client environment by switching to Chrome?

2) Could you delete all the layouts (including your customized form, mobile layouts etc ..) and use Nintex default form for desktop (not your customized Nintex form) and see if it is still slow. This is just to rule out that none of your customization's is actually affecting performance and even the OOB default Nintex form is also slow)

3) What is the RAM on your SQL server, is it always fully used?

4) SQL profiler might be able to give you some insights on the long running query (the only caveat is that you wont be able to change it even if you find the offending query as that would be native to Nintex!)  but it might help you to tune the indexes on SQL server (may be rebuild indexes etc)

5) On your client server try to see that you dont use load balancer (i.e. try to modify your hosts file) just so that you can rule out any Load balancer affinity issues. Divert traffic onto just one server (try all the web front ends to rule out any offending WFE).

hth,

Regards,

Shrini

Sorry to add another point (after again reading your post!)

6) You have 20 lookup fields? what is it configured on your web app resource throttling? is it default 12 ? I believe your Lookup fields might be causing the issue. I think the first step to check would be to reduce the lookup columns and to see if it makes any difference. I have created quite a few Nintex forms with 100+ fields (with quite a but of JS) so I am sure Nintex forms works well for large number of fields but so many lookups? Not sure .. this could be one of the thing you might seriously want to check.

Hi, thx for your answer !

The resource throttling idea was great, i completely forgot to think about that ... I increase the value to 40 and the results is much better (60 to 15 seconds), it is still too long but i will check what happens on SQL with my customer DBA this afternoon (i can't access the SQL server directly unfortunately for security reason). I think our SQL for development has a poor configuration and that might explain a few things. 

I also checked which lookups and i can possibly divide by 2 the number of lookups needed (30 to 15). I can replace some of them with choice values (i used lists because it easier to manage for my customer but if it affects performance i can explain that).

But your idea was good and i might find a way to get out of this mess .

I'll let you know as soon as it's fixed.

Xavier.

I forgot to mention that i alread tried to use a default Nintex Forms and it doesn't work (classic or responsive form). I also tried with another browser, on another computer and same results ..

What about the other options I mentioned, did you happen to check that? Lookup columns especially ..

Regards,

Shrini

Hi, i answered you but it seems that one of my answer needs to be moderated and is not published yet ... The resource throttling was really efficient but not enought so i try to decrease the number of lookups.

But i still don't know why it works using the preview functionnality or the SP default form ... We also checked the SQL performance and there is nothing wrong regarding the CPU or RAM usage but when i open the nintex forms it seems that there is a huge request that takes 15 seconds to load (SQL side) ... I don't what Nintex is doing that needs so much queries, SP seems to manage the same thing easily so ...

I will just remove some lookup column and replace them with choices, i can't do that for everything but it will help decreasing the loading time. That's really frustrating but unfortunately i can't spend more time optimizing Nintex OTB Afunctionnalities. I hope performance will be better on the production platform.

Thanks for your help ! I will let you know if i find anything else on this topic.

Xavier. 

Cheers .. I could not see your messages and for some weird reason I can only see your message on the community Inbox rather than the actual thread.

if you do reduce your lookups then things should improve overall. If you do get any other insights onto this then do keep me posted. It will be very interesting to know.

Regards,

Shrini

Hi,

Good to know resources throttling solved your issue, but to be on the safe side try to see if you can minimize the lookup controls as 12 is suggested by Microsoft for a reason as it would the absolute max as it would create a lot of joins to fetch any records.

Either ways not sure why the default form is quick enough, I don't think they can bypass the throttling rules ...

Lesser the lookup columns , lesser you may have to worry that it would work slow.

Thanks again for updating, issue like these are tricky and fun to troubleshoot as well

Regards,

Shrini

Hi @shrinivasnaik 

I am experiencing a smiliar issue. I do not have a lot of lookup fields but I have a lot of repeating fields. Could that be the problem?

Also, the form load very quick with Chrome, this problem is happening only on IE? How can I resolve that?

Thank you for your assistance!