tag:blogger.com,1999:blog-4126985520350746834.post2345239158767154718..comments2024-03-28T07:00:21.554+00:00Comments on Chris O'Brien: Office 365 performance – image renditions causing slow page loads in SharePoint OnlineChris O'Brienhttp://www.blogger.com/profile/10022906552670607366noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-4126985520350746834.post-71594906363465848292016-04-06T13:40:05.433+01:002016-04-06T13:40:05.433+01:00I spoke with someone at Microsoft, they tried to r...I spoke with someone at Microsoft, they tried to roll out a fix for the image rendition bug a few weeks ago...without success. They are still working on it. What we have done in some cases is to refer to the large thumbnail image stored in SharePoint ( _w and _jpg prefix)DJ Princehttps://www.blogger.com/profile/06891858193672149011noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-60483489188047957722016-04-03T20:28:33.530+01:002016-04-03T20:28:33.530+01:00Hi Stefan,
Cool, thanks for confirming!
Cheers,
...Hi Stefan,<br /><br />Cool, thanks for confirming!<br /><br />Cheers,<br /><br />COB.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-65190807923272850392016-04-02T15:10:15.079+01:002016-04-02T15:10:15.079+01:00Hi Chris,
checked it again and took a closer look...Hi Chris,<br /><br />checked it again and took a closer look at the images. You are right that they come from cache now. There must have been some changes applied on Office 365. A couple of weeks I struggled with the same problems as you described.<br />I checked it from Edge down to IE 10 and in any case the files was downloaded newly on each request.<br />I also checked several other browsers and Safari on Mac was the fastest on downloading and rendering the page the time was nearly the 50% quicker than others and TTFB was strangely better too.<br /><br />The same slow TTFB but that mostly depended on the tennant I tried it.<br /><br />Seems like they tweaked some stuff in the background because I had some realy strange troubles at this time.<br /><br />I'll keep an eye on this but so far I can say is that your solution is worth to be considered on the next branding project or as future improvements.<br /><br />/Stefan<br /><br /><br /><br /><br />Anonymoushttps://www.blogger.com/profile/10120468376896385118noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-438164501895677092016-04-01T14:22:06.576+01:002016-04-01T14:22:06.576+01:00Hey Stefan,
So I looked at this, but I don't ...Hey Stefan,<br /><br />So I looked at this, but I don't see quite the same thing. As far as I can tell, you're 100% right that the *page itself* is not served from the cache, but external resources such as CSS and JS files *are* served from the cache. I verified this in IE/Edge dev tools and also HttpWatch.<br /><br />You can see this at <a href="http://www.sharepointnutsandbolts.com/p/ieedge-network-trace.html" rel="nofollow">http://www.sharepointnutsandbolts.com/p/ieedge-network-trace.html</a><br /><br />So, I don't think this behaviour is too different to other browsers. But anyway, I guess the main thing is that broadly, the vast majority of files *will* be served from the cache on a non first time page load (as expected).<br /><br />Do you think I'm missing something, or do you also think that's the conclusion?<br /><br />Cheers,<br /><br />COB.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-84783655389691653552016-04-01T09:21:20.310+01:002016-04-01T09:21:20.310+01:00Hi,
found the post again and it is well hidden by...Hi,<br /><br />found the post again and it is well hidden by Microsoft. The information on how IE/Edge caches can be found on <a href="https://msdn.microsoft.com/library/dn265017(v=vs.85).aspx" rel="nofollow">Back Navigation Caching</a><br /><br />In there it describes how caching works in general and what the requirements are. One condition is that:<br /><i>Served using the HTTP: protocol (HTTPS pages are not cached for security reasons)</i><br /><br />This matches my review that Office 365 pages as well as other pages on Edge/IE won't be cached at all. This behaviour also can be reproduced by a network trace in IE.<br />While Chrome states on most assets of the SharePoint 'From Cache', Mirosoft Edge downloads all the things again and ignore the cache completely.<br /><br />/Stefan<br /><br />Anonymoushttps://www.blogger.com/profile/10120468376896385118noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-52640737551268589262016-04-01T08:07:58.856+01:002016-04-01T08:07:58.856+01:00Hey Stefan,
Good info, thanks. Yes, it's defi...Hey Stefan,<br /><br />Good info, thanks. Yes, it's definitely first-time page loads that I'm focusing on here (as I tried to make clear), hence testing with cache disabled. I wasn't aware there was a difference in IE/Edge behaviour compared to the other browsers - I'll try and look into this too, but what made you think this? Do you have any additional info? <br /><br />Thanks!<br /><br />COB.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-79975754085467404582016-03-24T17:25:06.549+00:002016-03-24T17:25:06.549+00:00Hi,
encountered the same problem recently in Offi...Hi,<br /><br />encountered the same problem recently in Office 365. The problem I've spotted doesn't come from the image rendition itself because SharePoint is realy quick to process the image renditions.<br />I the value for a single image rendition was between 5 and 30 milliseconds (SPRequest Duration) to process which is pretty quick and is the same time I got on on premises installation.<br />I think the problem more comes from the ASP.net and how SharePoint/IIS assembles the requests.<br /><br />In your traces, as far as i see in your screenshots, you have cache disabled, which is appropriate for two scenarios. The first is, when the user first hit the page because otherwise the images will be loaded from the local cache.<br />The second situation where the cache will be ignored is that the Internet Explorer/Edge is unable to cache locally on HTTPS Pages another really anying fact. All the asset in this browser will always be loaded from the server, which cause in really bad page performance.<br /><br />Overall all the rendering performance is not the best at the moment. Let's hope this will be fixed and changed soon.<br /><br />/Stefan<br />Anonymoushttps://www.blogger.com/profile/10120468376896385118noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-6330817807457878692016-03-23T11:24:47.764+00:002016-03-23T11:24:47.764+00:00I'd noticed the same thing myself - recently a...I'd noticed the same thing myself - recently as well. Renditions were working as expected until a few months ago, now they can take several seconds to appear.<br /><br />I wonder if there's a regression issue here, rather than the natural growth of their farms becoming apparent? It seems odd that there was an obvious step where the problem became apparent.<br /><br />It would be a shame if this is going to become a "just how things are now" aspect of SharePoint Online. Renditions were very useful and very quick to implement. Davehttps://www.blogger.com/profile/15245523145860887596noreply@blogger.com