Siebel IP16 – Browser Battle Benchmark

So – how does rendering performance has evolved with Innovation Pack 2016? I have been asked that question a number of times in the recent past. So, I put Innovation Pack 2016 on the rack, measuring Open UI’s response time per usual benchmark approach.

Again, four views with increasing complexity are used. Where really, the complexity of View 4 is ludicrous and primarily meant for stress-testing. In the past IE11 showed a non-linear pattern, that is why I included that impossible complex view.

Those ‘non-linear days’ are over due to largely IE11 specific framework enhancements included in IP15.3/14.9 back in September 2015. Based on my measurements we could say, that Innovation Pack 2016 does a slightly better job compared to IP15.3/14.9. Nothing spectacular. Call it stable.

meta-chart– Jeroen

Advertisements

Patch Set 15.3/14.9 Skyrockets Performance!

This result deserves truly a big applause. Oracle development worked closely together with Microsoft engineers to boost Open UI performance. With IP15.3/14.9 a complete overhaul of the List Applet renderer has been delivered. This went into the release quite silent, with no notice in the patch set’s release notes. The improvements were focused to give a boost for Internet Explorer, but the improvement is evident for Chrome (hence other browsers, including Edge) too!

Without more wording, just have a look at the results! These results are just amazing. We can safely say that Open UI will come close or exceed what you have ever experienced with High Interactivity clients. Think of the improvement it will make on mobile deployments for tablets… Skyrocketing performance.

IP153-149Performance

– Jeroen

Siebel Open UI – First Encounter With Edge

Windows 10, exciting enough? The atmosphere around Windows 10 is quite positive if you read the many articles which have been written. So, yesterday I took up the glove and downloaded the Windows 10 .iso file and today I created my first Windows 10 Virtual Box image. Without any pain, smoother than you can imagine. Click, click, click, done!

After having played around a bit, I decided to copy my Demo Quick Start environment across. That is the local dedicated client environment I often use, when I do not need a beefed-up server virtual machine.

Of course, there was one major reason for doing this: taking Edge to the test. My Demo Quick Start environment was functional without any pain. Well, that means for Internet Explorer it was working immediately! Since Edge is the default browser, I reckoned removing the /b (browser) switch should be enough to launch Siebel using the Edge browser. Wrong.

Luckily Richard from the SiebelHub faced the same issue. And the simple workaround would be to open Siebel in either Internet Explorer (or Chrome), then launch Edge and copy/paste the Siebel URL in that browser. Et voilá, works like a charm (as workaround then). Do not close the other browser, otherwise the Siebel client will be closed too.

SyngergyUI_Edge

Next I installed Chrome as well on the virtual machine, and was ready to run my usual performance benchmark test. Expectations are high, because while browsing with Edge some web sites it seems to behave pretty well. Added to this those recent positive benchmarks for Edge.

My joy changed into disappointment quickly. In this test Edge did not outperform even its neighbor. Really, it just behaving very similar to Internet Explorer. That means sluggish. Alright, back to Chrome. Immediately you get that feel of ‘souplesse’ back. Could it be Edge is so sluggish because it has Internet Explorer running in the background? Or does Virtual Box has a dramatic influence? Definitely it requires some more testing, but initial signs are not favoring Edge. Unfortunately.

Win10EdgeIEChrome

– Jeroen

Siebel OUI: Windows 10 + Edge – Ultimate Replacement For IE?

The team at Anandtech.com have produced a nice & updated comparison between the Edge browser which comes with Windows 10 and the usual suspects, Internet Explorer, Chrome and Firefox. Using the most common benchmarks. While I personally have little trust in Sunspider for obvious reasons from the past, apparently Edge performs particularly well according to Octane 2.0 too.

anandtech

It will definitely take a while before enterprise customers will move to Windows 10. The good thing is that Windows 10 will ship with Internet Explorer as well as the Edge browser.

Although Edge is brand-new, according to the HTML5Test it is still quite a bit behind on the competition. So less innovation than expected? This requires digging into a bit deeper at a later moment.

Anyways, eager to upgrade my Windows 8.1 laptop to 10 in the coming days 🙂

– Jeroen

Siebel OpenUI Performance – IE11 vs. Chrome Revisited

From time to time I run my benchmark tests. To see if technical improvements did materialize in tangible performance benefits. It has been a while I ran these, but with the general availability of IP15.1/14.7 I reckoned it would be a great moment to take a step back and compare apples again. The primary browsers are Chrome (R43) and 11.0.9600.17832CO Update 11.0.20 (that means including the June 2015 cumulative updated).

At this stage I compared three apples:

  • Patchset 14.4 (March 2015)
  • Patchset 15.0 (May 2015)
  • Patchset 15.1/14.7 (June 2015)

IP15.1 and 14.7 technically are build on the same code base. That means that all delivered code in these patch sets is 100% identical. But still, these are two different applications, right? Right. Because of the different repositories, other seed-data and items like additional themes the functionality is different. If you’d look at performance of both, it would make little sense to test them both. So I don’t. To make the comparison match, I will use the same Aurora theme (since the Synergy theme is non-existent in Innovation Pack 2014).

As a testing strategy I use my set of 4 views. These views range from little complexity to very complex. Still the simplest view is a parent-child view. Parent is a form applet with 99 (!) controls. The child is a list applet with about 80 (!) list columns. The most complex view has 4 form applets with each 99 controls, and 4 list applets with 80 controls. I would not recommend creating anything like this for production use, but as matter of comparison it works just fine.

To measure the time it takes to build the view, I use a measurement framework. Which basically times the lapse between “preload” and “postload”. The time lapse between these two events consumes the majority of the time spent in the Open UI framework. It does exclude CSS processing though. I take the measurements always on an unloaded system. And I have a clear look at the task manager too, to ensure CPU shows low levels of activity. To get accurate figures, I take a number of samples. Looking at the Standard Deviation will tell whether the measurements have potential outliers or not.

PerfMeasSo what are the results? First of all, the difference between IE11 and Chrome remains about a factor two. This is quite a stable factor over the past year. All the efforts MS has put into IE11 has not moved it much closer to its rival.

That is what the graph tries to tell. For example: IE11 consumes 209% of the time Chrome does for the most complex view view on IP15.0.

perfIEChromefactor

That said, if we set all measurements side-by-side you get a grasp on the evolution. There is clearly a declining line between 14.4, 15.0 and 15.1. Interestingly, there is a big improvement for IE11 on 15.1/14.7. I did take these measurements a couple of times to be sure. But true, there is quite a significant improvement for IE. Hooray!

This all demonstrates the efforts Oracle development is putting in materializing improvements in performance. This really is not a simple task, since the Open UI framework heavily relies on JQuery. And there are many JQuery patters (e.g. JQuery selectors) which can be extremely costly for JQuery. But also smaller things like “for” loops, which tend to be 20% slower than “do-while” loops. Imagine if you have loops over large objects or arrays, that can count up (and it does).

Here are the results.

IP144-150-151-IE11-Chrome2

Enjoy the weekend or your holidays!

– Jeroen

Siebel IP14 – PS4 Has Some Performance Tricks Up Its Sleeve

A few posts back I reported about Microsoft to release a performance fix for Internet Explorer 11. Tonight I completed my initial tests with the Siebel Innovation Pack 2014 Patch set 4 which Oracle released a couple of weeks ago. The Patch Set 4 release notes make note of two particular bugs which should improve OpenUI view rendering performance. So I picked up the glove and executed my usual set of performance review scenarios. I compared Patch Set 2 against Patch Set 4, for the usual set of browsers. I ran each test three times to cancel out any measurements which could have a (too) high standard deviation. The cool thing is that the performance measurement framework does all the heavy lifting for you. Duncan discusses this simple but very effective framework in the Open UI Developer’s Handbook too.

IE11PerfFigures

Bottom line? All browsers benefit from the Patch Set 4. IE11 benefits most. But still IE sits all alone silent in corner. Internet Explorer – despite the performance hot fix being applied – remains no competition for Chrome and Firefox.

IP14PS4PerfCompAgain Chrome outperforms all, with significant improvements. These improvements alone should make you to consider Patch Set 4 strongly.

– Jeroen

Dromaeo benchmarking – IE11, FF R31, Chrome R37 and Canary

Besides Google’s Octane 2 there is another extensive benchmarking framework: Dromaeo.

I took it to the test for the usual suspects.

The good thing about Dromaeo is that it has dedicated tests for jQuery, very useful with OpenUI in mind 🙂

And the results are… I ran a number of tests on my good-old i5-2520M@2.5Ghz. I ensured while running the test the machine was idle.

DromaeoFrameworks DromaeoCoreDOM DromaeoJslib

The tables list the number of runs/second for the different test dimension. From those I calculated the performance factors. So “Chrome vs. IE” has a performance factor 2,9 for the “DOM Attribute (Prototype)” dimension. So Chrome R37 is 2,9x faster than IE11 for this particular characteristic.

It is clear that IE11 overall is being surpassed by its rivals. Especially when looking at the relevant dimensions for Siebel Open UI (jQuery) Chrome is the overall winner. For jQuery DOM Query/selector operations Firefox and Chrome end up ex-aequo. More general the jQuery framework is better tailored for Chrome. The more all-purpose DOM operations are best tailored for Firefox (these entail direct DOM operation without using any framework).

On generic DOM traversal IE11 is tailing its rivals.