WWB19 slow with huge form

[viper83viper]

Hi,

I created a form for my company (internal use only) with hundreds of checkboxes and LayoutGrids. The form became bigger and bigger, but with such a huge amount of checkboxes, WWB19 became very slow. So slow it looks like you play a game with 3 frames per second... Selecting text is difficult for example.
Other smaller projects are fine and fast.
When I hide some LayoutGrids, including the checkboxes within, it is a little faster. But they will not publish anymore. Also I can not see my hidden objects only, when right clicking on the Object Manager.

I understand that publishing takes some time.

How can I make my project/WWB run faster?

(you probably will ask for a demo project, however there is sensitive information in this project, hence I can not share on this public forum. I can share privately?)

Thank you!

[Pablo]

There is no option to make the software faster, it already uses direct2d for optimized rendering. Some elements just take some time to calculate and render.

You can send your project to pablo@pablosoftwaresolutions.com, so I can take a look if I improve the software in the future based of what you have done.
However, this is not something can that can be done quickly, it may require a redesign of core functionality which may take months of works.

Also, note that no matter how much optimization is done, eventually there will always be a limit to how much elements you can add.

But maybe you can divide your form into smaller pages?

[viper83viper]

Thank you!

I totally understand.
I thought about dividing into smaller pages, however the form also needs to be printed to pdf. I am not aware if thats possible with multiple pages.

Do you have any tips on the hidden objects, in the object manager? This helps to make it a little faster.

Thanks again!

[Pablo]

The only other way I can think of is by using custom code. For example, by collecting the data of each form in a PHP session and then process all data on the final page.
But this cannot be done 'visually' and requires programming

In the context menu of the Object Manager you can select whether you want to see visible or invisible objects only.
https://wysiwygwebbuilder.com/object_manager.html

[wwonderfull]

In my understanding as it was mentioned that there were hundreds of checkboxes meaning those are not optional ones more like multiple choice checkboxes that means they will have that many columns at the same time there are edit fields and others so it will for sure have performance issue form data the script of wwb just posts it to the db on the server now the server is the one who processes it and takes it in to the database. Always remember if the data is too much then it will take time and for sure have performance issues. I would have tested it using the developer tools at the same time you can try doing a small test.

1. Try sending the data into a csv file if it has textual data only and if the form data is csv compatible. In that way you can see how fast the data goes in to the csv.

2. Use localhost XAMPP or WAMP to test and see how fast the data travels locally.

In that way you can determine if your forms data is too large, or the internet speed is the matter or if the server is lagging the performance. You can figure it out quickly.

[viper83viper]

Thanks again (both)!

Here is my challenge with the hidden/visible objects: https://1drv.ms/i/c/a4f6e4bf08096abd/EZ ... w?e=4g26bC

@wwonderfull; when the form is submitted, I receive the data in 3 seconds! So it is not the processing which is slow, it is WWB19. Selecting, dragging and adding things is very slow. But like Pablo said, there is just so much you can add, which I understand.

Regards,

[wwonderfull]

The data is supposed to come that quick for sure even if you sent a 745 words 4,984 characters of text data which is approximately 4 kilobytes.

What I thought was it was taking a lot of time like 10, 20 or 30 seconds which is uncommon issue. So, nothing to worry about much. But yes in wwb the dragging can become a bit laggy if there are too much nested elements.