Easy Profile - Joomla Extension

Hi,

As far as I would say, this should not be a too heavy load on the system?

Yes this is possible, but 800 users is not a lot. A normal shared webserver should take less then 5 seconds.

Have you a possibility to increase "memory_limit" in PHP.ini? in a production site you should have "256M". You can check this limit at Administration->System->System Information->PHP Information, search "memory_limit" line

Thx for your reply.

Unfortunately, the memory limit was already 512, we even increased it to 1024 but that did not help.

Hi,
if you can send me your backend details (I wait if possible from post at https://www.easy-profile.com/support/blank-screens-on-some-actions-not-sure-if-easyprofile-related.html) then I can investigate about this (maybe there are some user plugin that create problems)

Sorry, it took some time to get back to you.

We've set up a test site, see the details section.

Also I forgot to tell you that we use the option to export Readable values. When using Importable values the result is ok - though we also think that the processing is not very fast.

I hope that the test site will help to solve this issue.


Kind regards, Frits

Hi,
I have just tried and works, but you have right, this process take a long time (Read Note above). In future We will change the process from 1 call to many ajax call to avoid PHP time limit execution exceptions.

NOTE: I don't know why it is so slow, but probably this is due to a slow shared hosting performance. In my test the exportation process take 1min 15sec, and in your PHP you have limit set to 99sec (1min 39sec). This mean that if you have many connections in your site the exportation process may require a higher time than normal, so it may exceed PHP time limit execution.

Solution for now:
in file /administrator/components/com_jsn/jsn.php at line 15 add this code to increase PHP max execution time only for Easy Profile Backend

ini_set('max_execution_time', 300); //300 seconds = 5 minutes

We do not recommend to increase max_execution_time directly in PHP.ini (PHP configuration file) because this affect all your site and this is not secure (can create performance problems), now you have 99, recommended is 30.

Hi,

Adding that line solves the issue indeed, so we are happy that we can deliver these exports as needed.

Yet I do hope that this can be solved in an other way. Also, it seems to me that this is quite a long time for an export; it really surprised us. I can understand that creating a readable file will take some extra time but also the importable file is slower that I would expect.

If you change the process by chopping it up in multiple, smaller parts, would you think that the total running time will decrease?

Kind regards, Frits

If you change the process by chopping it up in multiple, smaller parts, would you think that the total running time will decrease?

Unfortunately no, but this remove timeout problems, basically each request add 10 users at a time to CSV file, but the timing is the same.

Requests via Ajax allow:
- No timeout errors
- No memory limit errors
- Possibility to add some UI improvements like Loading icon and/or Loading bar (so system no longer seems freeze)

Of course when we put hands to export system we will try to find some performance improvements