Forums

Forms Manage loading large forms very slowly

jcalvert 20 Jan, 2016
In the Forms Manager when I click to load a large form it takes over one minute while the "LOADING" circle is spinning.

This did not happen with the same form in V5 under Joomla 2.5... it loaded fast.

This is also happening with another large form, so it's not the form itself – it appears to be the size that's the problem.

The large form is 66 KB when exported. Another form that is ~25 KB loads very quickly.

What's going on? Is there a PHP parameter that I should increase??

thanks,
JC
jcalvert 20 Jan, 2016
More info...

It doesn't matter if I have "Safe Save" on or off... same result.

What should I use for "Safe Save", "Safe save chunk size", and "Safe loading count" ?

thanks,
JC
jcalvert 20 Jan, 2016
I played around with chuck size and loading count.

I increased my PHP max_input_vars from 2000 to 4000, and tried chunk size 3950... still didn't work.
Then I just turned Save Save off... still doesn't work... still takes over a minute for the Forms Manager to load the form.
GreyHead 20 Jan, 2016
Hi jcalvert,

It certainly can take a long time for larger forms to load - but this seems to me more a function of the server speed and responsiveness than anything else :-(

Bob
jcalvert 20 Jan, 2016
1 Likes
Sorry... I was simultaneously testing the very same forms on the Joomla 2.5 site and they loaded right away.

I manage the server myself... it's a very speedy dedicated server with few sites on it.

I am mystified by this problem. It couldn't possibly take over a minute to load one of these forms. Something is wrong.

Here's the form in question: http://smvhs.org/4la-reservations

JC
GreyHead 20 Jan, 2016
Hi JC,

It loads here from scratch in 2.5-3 seconds.

Bob
jcalvert 20 Jan, 2016
Hi,

Sorry, I probably should have used the word "opening", not "loading"... I'm talking about in the Joomla admin, ChronoForms component Forms Manager, when I am clicking on the form to open the form. It takes over a minute for the "LOADING" circle to stop. Other forms are fast, and in Joomla 2.5 this same form opened fast. Now for some reason in Joomla 3.4 it is very slow.

JC
GreyHead 20 Jan, 2016
Hi JC,

If you check in your web browser developer tools do you get any clues about what is taking the time to load?

Bob
jcalvert 21 Jan, 2016
Thanks for that tip.

Using FireFox console I can see 44 POSTs that are loading the form HTML, each taking about 1.5 sec each, adding up to the 1+ min. that I observed.

I see what the problem is now. Even when I turn Safe Save off, it's still active, apparently triggered by the "Safe loading count" which defaults to 20. I increased the loading count to 10,000 and the problem went away... the form loads in about 10 seconds now.

So, it looks like a bug – Safe Save "No" should turn off the feature regardless of the loading count.

I have confirmed that this problem didn't exist in ChronoForms5 5.0 RC4.1, because there was no safe loading count setting in that version. This is why my Joomla 2.5 sites didn't have the problem.

Thanks for a great extension all these years! ... much appreciated.

JC
jcalvert 21 Jan, 2016
I forgot to mention, there was also an error reported:

Error: Syntax error, unrecognized expression: #general-{N}
jquery.min.js (line 2, col 12731)


Which I have traced to the following code in ./administrator/components/com_chronoforms5/chronoforms/actions/image_resize/image_resize.php

<li class="active"><a href="#general-{N}" data-g-toggle="tab"><?php echo l_('CF_IMG_RES_GENERAL'); ?></a></li>


JC
GreyHead 21 Jan, 2016
Hi JC,

Thanks for both if those updates - hopefully Max will fix the Safe Count one in a future version. I hadn't seen that problem before.

Maybe also the JS error - though that seems to be harmless??

Bob
nfncmg 25 Jan, 2016
This is promising!! I was about to give up.

My form when exported (by exported, you mean take a backup right?) is only 50k.

I click my form to bring it up in the wizard and I see this in the Apache logs:
127.0.0.1 - - [25/Jan/2016:17:55:46 -0500] "GET /administrator/index.php?option=com_chronoforms5&act=edit&id=20 HTTP/1.1" 200 2064759 "9 secs"

If only 9 seconds is really the time I had to wait for the form to come up for editing.

By the time the form completes its loading and is ready for editing, I have 60 entries similar to these:
127.0.0.1 - - [25/Jan/2016:17:56:17 -0500] "POST /administrator/index.php?option=com_chronoforms5&act=render_field_config&tvout=ajax HTTP/1.1" 200 2902 "0 secs"
127.0.0.1 - - [25/Jan/2016:17:56:17 -0500] "POST /administrator/index.php?option=com_chronoforms5&act=render_field_config&tvout=ajax HTTP/1.1" 200 16272 "0 secs"
127.0.0.1 - - [25/Jan/2016:17:56:17 -0500] "POST /administrator/index.php?option=com_chronoforms5&act=render_field_config&tvout=ajax HTTP/1.1" 200 4388 "0 secs"

Most of the POSTs are about 16k in size. You can see the total time too over a minute to complete. This is on initial loading and when I save the form.

If I turn off Safe Save and/or try changing any of the parameters for Safe Save, the form loads quicker. Unfortunately, the Setup section for the form is blank so the form no longer functions.

-Is there any way to edit large forms efficiently using the Wizard? Dragging and dropping, creating new containers, etc has become almost impossible.
-What exactly makes a form a "large" form?

V5.0.10 on J 3.4.8
GreyHead 26 Jan, 2016
Hi nfncmg,

Have your tried changing the max_input_vars setting in your PHP configuration?

If you do that then you may be able to disable the Safe Save.

It's hard to say what constitutes a 'large form'. The problem is that everything you see in the Form Editor is a part of one very large form - each option in each from element or action is a form input - they can quickly add up to give a form with thousands of inputs. Many times more than the form you are creating. I've seen thousands of forms now on hundreds of servers and 99% of the time everything loads smoothly - sometimes with 20 or 30 seconds of the grey loading page. When it takes longer than that it seems to be either an over-loaded server or PHP limits, or server security settings.

Bob
This topic is locked and no more replies can be posted.