Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: Unresonable(?) Execution Time Increases w/ Publisher Enabled

Status Resolved
Add-on / Version Publisher 1.1.3
Severity Trivial
EE Version 2.7.2

Nick Benson

Dec 23, 2013

Long story short, when Publisher is enabled, the “Total Execution Time” from EE’s profiler is increasing 0.135 sec (a blank template) to 0.150 (a fairly complex page). Any tips/suggestions for decreasing Publisher’s impact on a page load times? The impact was significantly worse last night, before upgrading from 1.1.12 to 1.1.13 (execution times were approaching a second, even w/ caching enabled, and dropping to 0.22 or so w/ Publisher disabled).

In the event of the complex page, I’ve got CE Cache enabled, and the execution time is averaging 0.371 sec with Publisher enabled, and 0.220 without.

The rest of the add-on stack, if helpful:

ajw_datagrab
assets
blueprints
categories
ce_cache
ce_img
ce_img_aws
ce_str
detour_pro
devotee
entry_analytics
fieldpack
gmap
gmap_geocoder
gwcode_categories
ifelse
low_events
low_search
matrix
mustash
page_number
playa
proform
prolib
publisher
publisher_drivers
safecracker_file
snippet_sync
stash
structure
superfish_admin
switchee
url_helper
wb_category_select
will_hunting
wygwam
zoo_flexible_admin

This isn’t red-hot urgent, but would like to know more within a week, if possible; don’t miss time with friends/family over the break on account of this.

I cannot provide FTP/site access on account of a VPN, but, I’m happy to email you dumps of profiler output or anything else that might be handy, if any of what I’ve said sounds unusual.

#1

BoldMinded (Brian)

I know page load times are important, which is why I’ve started adding more cache options, but a 10th of a second increase isn’t much in the grand scheme of things considering what publisher is accomplishing. URL translations will yield the largest increase in page loads due to what has to be done to make that feature work, and it’ll be the target of caching in the next release or two.

#2

Nick Benson

Indeed, certainly not a deal-breaker with where it’s at now, but, it is accounting for 40% of the page execution time, so any improvements would be greatly appreciated, obviously.

Thanks for taking a look, have a great holiday! Feel free to mark as resolved.

Login to reply