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: High resource usage with Bloqs/Publisher

Status Resolved
Add-on / Version Bloqs 4.0.1
Severity
EE Version 4.2.3

Bloom Agency

Oct 12, 2018

Publisher version: 2.8.2

Hi,

We’ve recently noticed on both a clients staging and live server that a combination of bloqs & publisher is taking up masses of resources and actually bringing down the sites when caching is disabled. The reason we believe it to be a bloqs/publisher combination is that there is 6 second time delay between Calling Extension Class/Method’s occurs between a bloqs/publisher combination.

As these are client staging / live servers, I unfortunately cannot provide you with any credentials to access the CMS and/or the server.

Below is a debug log from the server showing a big gap in between executing / calling the two methods/classes

§  0.108285 / 4.5MB Blocks: fetching blocks for “blocks|fetch|entry_id:113;field_id:54”
§  0.108828 / 4.5MB Calling Extension Class/Method: Publisher_ext/blocks_get_blocks <———- Suspected issue.
§  6.438070 / 11.6MB Calling Extension Class/Method: Publisher_ext/relationships_query <———- normal load time between calls resumes after this.
§  6.452893 / 11.9MB Calling Extension Class/Method: Publisher_ext/relationships_query

Are there any known issues with high cpu / server usage when using these two plugins in combination?

Please let me know if I can provide you anymore information / logs that would be useful.

Thanks,

#1

BoldMinded (Brian)

Hi there. You’re a few versions behind on both add-ons, so I’d recommend upgrading first before proceeding with the ticket.

#2

BoldMinded (Brian)

It also may help to share how many blocks and what sort of blocks are on the pages that are slow… screenshots or something. There is also a query log… share any queries that hit the exp_blocks table. You can also debug the queries by prefixing it with “EXPLAIN select from …” and running the query in phpMyAdmin, SequalPro or whatever, which outputs some info about the query itself.

#3

Jaywing Developers

Hi Brian,

Thank you for the swift response. I will test this on staging this afternoon and then report back Monday with any discrepancies we notice from over the weekend.

Thanks,

#4

Jaywing Developers

Comment has been marked private.

#5

Jaywing Developers

Comment has been marked private.

#6

BoldMinded (Brian)

Nothing in those screenshots seems out of the ordinary. Seeing the query EXPLAINs would be helpful. Also, do you have Publisher’s cache enabled, or any caching at all on the site?

#7

BoldMinded (Brian)

Those screenshots don’t really show what atoms the blocks contain. What are those blocks composed of? A lot of Relationship, Assets or some other complicated fieldtypes?

#8

BoldMinded (Brian)

Closing this out due to no response in over a month.

Login to reply