Symphony.

Any idea if this is high load time for job_table?

• login 0.0030 s from 4 queries sessionmonster_addgettosession 0.0017 s from 1 query banners 0.0169 s from queries job_table 2.4074 s from queries languages 0.9112 s from queries navigation 0.0203 s from queries number_of_jobs 0.1176 s from queries number_of_jobs_full_time 0.1660 s from queries number_of_jobs_part_time 0.0859 s from queries sessionmonster_showsessionparam 0.0002 s from queries get_company_logo 0.0531 s from queries

job_table 2.4074 s

That looks pretty high to me.

Ye thought so..

Any hints on reducing it?

Can you paste the PHP of the DS file (workspace/data-sources/data.job_table.php) onto Pastie so we can see what it’s doing.

How many entries are there in that section?

http://pastie.org/773518

Here you go!

Allen helped figured out the need for this line using a shared host db $this->_Parent->Database()->query(“SET OPTION SQL_BIG_SELECTS=1”);

As the url params were not allowing all of them to work.. it reached a limit.. this is not the issue.. I also noticed the languages ds was around the 2.090s load time but I just put cachelite on the 2.0.4 install and the times for all ds are down to 0.788 or there abouts!

EDIT

Max of 12 entries at the moment.. each one has an image attached but JIT is sorting out the images size for us!

EDIT

Visible Entries/Approved Entres 12.. actual Entries in section from admin area I about 70ish

Is the filter '149' => 'yes' on a checkbox field? If so, how many entries do you have in your section? I have found once you pass several thousand the filter on a checkbox can be slow.

Glad to hear CacheLite is solving your problem.

You might also want to investigate caching of specific DSs since it looks like you’re providing dynamic sorting which CacheLite might not work with fully.

Yes ‘149’ => ‘Yes’ is a checkbox and entries = 93 of which 12 are currently active.. I do have the ‘84’ => ‘equal to or earlier than {$today}’, ‘85’ => ‘equal to or later than {$today}’,

Filtering out the entries that should not be shown! This is based on entry-to date field being later than {$today} so as to include entries that haven’t reached a closing date..

Oh well. It shouldn’t have an impact when entry counts are so low.

Chances are the load times are high across the board because your server was suffering at the time the page loaded.

Monitoring the loads for a bit to see what’s occurin like! cheers for the heads up!