Thread

Brandon - also, I’d like to thank you for looking at this from your end as well.  It’s much appreciated!

I also want to thank Brandon… his personal customer support is top-notch!

I did some more testing as Lisa suggested.

I first tested to see how long it takes EE to render this page under normal conditions:
http://www.pbinsight.com/products/location-intelligence/applications/mapping-analytical/mapinfo-professional/

Script Execution Time: 1.5146 Queries: 101

Then, I saved a minor change to this entry via the EE control panel. I didn’t even change any relationship data.

I then reloaded the same URL:

Script Execution Time: 97.1351 Queries: 630

Subsequent reload of the same URL:
Script Execution Time: 1.4970 Queries: 100

Brandon has already contacted me directly with some code samples to try. I will circle back to this thread after I’ve been able to test the code. Fingers crossed!

We’ll be here!

Brandon has already contacted me directly with some code samples to try. I will circle back to this thread after I’ve been able to test the code.

As I noted on GitHub, that change won’t speed up entries that were updated, and will only marginally effect entries which relate to the updated entry. Whether or not the relationships were changed makes no difference. The goal was to keep the rest of the site from slowing down due to one updated entry.

Thanks Brandon, we have the code in place now.

I did the same test again with the same piece of content.

Script Execution Time: 51.1352 Queries: 635
Script Execution Time: 49.9664 Queries: 641

I also requested other pages than the one updated and they seemed fine, which is great.

What can be done to improve the performance of the first load of a piece of content after it’s been edited? 50 seconds is way too long to expect any visitor to wait and most of them will assume the site is down or there is some other problem.

Is there a reason this edited item’s relationship cache can’t be refreshed after the entry is updated?

It should be cached on entry/edit- though I noted in the other thread that multi-edit is an exception to that.  Testing it myself on a clean install- editing an entry doesn’t wipe the cache table (and in the case where it does for the single entry, it rebuilds it upon submission).

Can you test this with all extensions disabled?  Something just seems weird in the way the site is behaving.  I laid out a list of what I’d expect to clear out the relationship table in the other thread- a simple single entry edit wouldn’t normally do it.