kernel/object.php get() may be requested several times in one page load and you cannot be sure that 0,0001 result is from the call you made from smartsection. The result will be for the last piece of code that runs a $handker->get().

I think you should try to find $objs=$handler->getObjects(); and $objs->toArray();

This methods when used with little care can waste many memory and the toArray() can be time consuming when rendering text areas on many objects. Probably you will find that toArray is used even when no text area is displayed, look into blocks.
Also,there is a create and drop table in smartsection front page that is very heavy.

I have removed all calls to getObjects and toArray because yes, these would be expensive methods to execute.

What worries me is the time taken to execute $obj->get() increases as the number of rows in the database increases. In addition, the amount of memory required by PHP to execute the page also grows.

The code I have shown above is all that I am executing and the Total time required by XOOPS to load the page is 6 seconds (on average), whereas a fresh install of the module with very few rows ( < 100) probably takes 1seconds to render.

Sorry for the late reply!

If you look at smartsection/class/item.php you will find that the get() method is overriden and calls assignOtherProperties();

The assignOtherProperties() will get a category and a permission handler and perform extra logic.

The permission handler will get permissions for that item, is not a problem.

The categories handler will get all smartsection categories as objects and if you look into it, the getObjects() is also overridden to get corresponding permissions. Since it use static variables this will happen only once in a request but it will still be a problem for large database sets.

Bottom line, while you think you are asking for just one object, you are asking for hundreds of them.

Hi lolpant,

Did you have any progress with resolving this?

Did you perhaps find another module that does the job as well or better?

Regards,

mekano

Smartsection had a lot of problems.

Switch to Publisher. You can import from smartsection and it works great. I've got over 20,000 articles in mine with no delay or performance issues

You will find it very familiar as Trabis basically re-did smartsection with a lot of performance improvements