Perfomance issues [Reading of templates not cached in J2.5]

Miken
Offline
Premium Member

11 years 1 month ago #40600 by Miken

Replied by Miken on topic Perfomance issues [Reading of templates not cached in J2.5]

ggppdk wrote: Hello

r1781 has a very optimized frontend/backend

about your question

on second run this number should be close to zero is it not ?

have you disabled caching in FLEXIcontent component parameters (this is in the first TAB called "options")

I updated the component.

The first launch:

Code:

** [Flexisystem PLG: Auto Checkin/Auto state(e.g. archive): 0.00 s] 
0.000 seconds (+0.000); 8.62 MB (+8.616) - START: FLEXIcontent component
0.631 seconds (+0.631); 17.54 MB (+8.929) - END: FLEXIcontent component: (VIEW: category)
-- [Initialize component: 0.05 s] 
-- [Execute Main Query: 0.01 s] 
-- [Execute Secondary Query(-ies): 0.00 s] 
-- [FC Templates Parsing (cacheable): 0.46 s] 
-- [FC Fields Value Retrieval: 0.01 s] 
-- [FC "category" view Template Rendering: 0.03 s]

Second launch^

Code:

** [Flexisystem PLG: Auto Checkin/Auto state(e.g. archive): 0.00 s] 
0.000 seconds (+0.000); 8.62 MB (+8.616) - START: FLEXIcontent component
0.621 seconds (+0.621); 17.54 MB (+8.929) - END: FLEXIcontent component: (VIEW: category)
-- [Initialize component: 0.05 s] 
-- [Execute Main Query: 0.01 s] 
-- [Execute Secondary Query(-ies): 0.00 s] 
-- [FC Templates Parsing (cacheable): 0.45 s] 
-- [FC Fields Value Retrieval: 0.01 s] 
-- [FC "category" view Template Rendering: 0.03 s]

The third launch(advanced cache disabled):

Code:

** [Flexisystem PLG: Auto Checkin/Auto state(e.g. archive): 0.00 s] 
0.000 seconds (+0.000); 8.61 MB (+8.612) - START: FLEXIcontent component
0.622 seconds (+0.622); 17.53 MB (+8.917) - END: FLEXIcontent component: (VIEW: category)
-- [Initialize component: 0.05 s] 
-- [Execute Main Query: 0.01 s] 
-- [Execute Secondary Query(-ies): 0.00 s] 
-- [FC Templates Parsing (not cacheable) : 0.46 s] 
-- [FC Fields Value Retrieval: 0.00 s] 
-- [FC "category" view Template Rendering: 0.03 s]

There is no difference. As more than 0.6 seconds and remains

Flexicontent 3.1.1 & Joomla 3.7.1

Please Log in or Create an account to join the conversation.

ggppdk
Offline
Administrator

11 years 1 month ago #40604 by ggppdk

Replied by ggppdk on topic Perfomance issues [Reading of templates not cached in J2.5]

Hello

this is not normal for some reason Joomla cache is called but it returns non-cached data

prior to calling the cache we force it to be ON and to be have a expiration of 24 hours,

so if the cached function call fails it must be for a different reason,

e.g. your Joomla cache folder is not writable ? or does not exist , etc

-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star...

Please Log in or Create an account to join the conversation.

Miken
Offline
Premium Member

11 years 1 month ago #40607 by Miken

Replied by Miken on topic Perfomance issues [Reading of templates not cached in J2.5]

ggppdk wrote: Hello

this is not normal for some reason Joomla cache is called but it returns non-cached data

prior to calling the cache we force it to be ON and to be have a expiration of 24 hours,

so if the cached function call fails it must be for a different reason,

e.g. your Joomla cache folder is not writable ? or does not exist , etc

You were right. folder cache was not available to record :idea:

Flexicontent 3.1.1 & Joomla 3.7.1

Please Log in or Create an account to join the conversation.

ggppdk
Offline
Administrator

11 years 1 month ago #40609 by ggppdk

Replied by ggppdk on topic Perfomance issues [Reading of templates not cached in J2.5]

Hello,
ok , thanks for feedback

also, please note that in J3.x we use a different way for parsing templates,
which uses raw PHP XML file parsing which is very fast and does not need caching

(this because in J3.x developers choose to do this and remove the old built-in classes for parsing XML files)

*(e.g. in your case (for J3.x.) it would be without caching about 0.02-0.03 seconds)

Please Log in or Create an account to join the conversation.