It won’t take much longer before Siebel Innovation Pack 16.0 will see the light, and will be made generally available! Last week I have been enjoying the yearly field enablement sessions conducted by product development. Innovation Pack 2016 has quite a full bucket of enhancements, and of course there are very visible enhancements, as well those which are less so.
Why is this so relevant – think of these scenarios
- Working with Siebel from remote locations as where the Siebel Enterprise is located, incurs by definition an increased server round-trip time (RTT) also known as latency. Latency can have a significant impact when the number of resources required by a web page increases.Although most Siebel resources are relatively small, and will be further compressed to transfer even less physical bytes – there are larger resources (think of the main theme/stylesheet, the JQuery framework). These large resources will require several server round-trips each to make it to the browser, as typically the TCP/IP Window size is or starts at 64KB.That TCP/IP Window size becomes more of a topic when latency is on the rise. Windows 7 and later and for that matter iOS and Android have the notion of TCP/IP window scaling, which in particular helps downloading files faster over larger distances. This benefit materializes for larger files. Everybody has seen the effect, where starting a download from a remote location initiates slowly and then gradually accelerates – this is window up-scaling kicking in.
But for the majority of the Siebel resources, up-scaling helps only a bit. Bringing down number of resources, brings way more weight on the scale.
- Second, the sheer fact that many scenarios exist where the browser has no prior cached content. Many IT organizations explicitly choose to wipe the browser’s cache, when the user logs of Windows. Typical situation seen at customers deployed on Citrix, where cleaning the cache is common business.Similar situation often for mobile devices, where mobile device management solutions (MDM) wipe browser caches regularly.
Given this context and how it affects Siebel customer today, Siebel development took up the glove and had for IP16 a close look at the status-quo.
The primary goal was to improve login time with non-cached content
Because the login time has a significant impact on the overall user experience. If you reduce the login time, you improve user experience at the very same time. Once logged-in, additional files might be required on-request. Better to ‘lazy load’ these than upfront. Once Siebel has all static content available, it will work efficiently. A simple view navigation costs as little as 5 KB and would only take a single round-trip. Of course, we have to watch out with those GetProfileAttr() calls, and using dynamic “CanInvokeMethod” enabled/disabled buttons. Such configuration can become costly, requiring several additional round-trips.
So, here are the sheer figures measured by me on a reference IP15.10 and IP16.0 environment (not being the final build). Total size during logon process has been reduced from 7.4 MB to about 1.7 MB. A reduction of roughly 75%. Mileage may vary here, since I have been testing against a pre-production release of IP16.
Taking the improvements together, they materialize in substantial faster logins. But here mileage may vary a lot too. I measured from my location about which is about 150-160 milliseconds round-trip from the target servers through a VPN. The further away, the deviation between IP15 and IP16 will increase further. The more close to your target, deviations will become lesser. It turned out IP16 to be approximately 34% faster compared to IP15.10 in my scenario. Logging-in with the same user, landing on the default home page.
See below further details:
In the coming weeks, I will be posting more on Innovation Pack 2016!