(858) 586 7777 | About | Testimonials | Contact
vteams vteams vteams vteams
  • How does it work?
    • Startup Process
    • Your First Day
  • Technologies
    • Hire PHP Developer
    • Hire App Developer
    • Hire JavaScript Developer
    • Hire ROR Developer
    • Hire IOS Developer
    • Hire .NET Developer
    • Hire AI Developer
    • Hire Robotics Engineer
  • Sample Budgets
  • Meet The Team
  • Experiments
  • Captain’s Log
  • Blog
vteams vteams
  • How does it work?
    • Startup Process
    • Your First Day
  • Technologies
    • Hire PHP Developer
    • Hire App Developer
    • Hire JavaScript Developer
    • Hire ROR Developer
    • Hire IOS Developer
    • Hire .NET Developer
    • Hire AI Developer
    • Hire Robotics Engineer
  • Sample Budgets
  • Meet The Team
  • Experiments
  • Captain’s Log
  • Blog
Blog
  1. vteams
  2. Blog
  3. Telerik Report Rendering Process Performance Issue
Jul 30

Telerik Report Rendering Process Performance Issue

  • July 30, 2015

A web-based commercial and SBA lending software was developed that manages the origination, processing, closing, and monitoring of small business loan portfolios. With the loan management system, lenders can think big and reimagine what modern business lending can be. It was developed by using Microsoft Visual Studio 2013(.NET 4.5), Bitbucket (Git), ASP.NET MVC, C#, Web API, MS SQL Server 2012, Single Page Application, Kendo UI Controls and Charts, Telerik Reporting, jQuery, Backbone.js, Marionette.js, Require.js, Underscore.js tools and technologies.

Problem:

Telerik report rendering process was considered too slow.The reason was discovered to be that the ICache caching technique was implemented for Telerik reporting, but the report rendering process was very slow. The Client wanted vteam #397 to analyze the problem and implement its fix, so the overall report rendering process needed to be improved.

Solution:

During R&D, it was found that Telerik Reporting provides caching mechanism using two techniques:

1) ICache:

ICache is a legacy caching approach and it does not support multiple service instances deployment.

2) IStorage:

IStorage is a preferred storage method by Telerik Reporting over ICache due to its enhanced functionality, allowing the service multiple instance support and specific implementation (MS SQL Server Storage) for MS SQL Server.

IStorage approach requires extra tables (if database approach is used) and a locking mechanism is provided which guarantees the serialized state access.

Comparison:

IStorageICache
IStorage is specifically designed/developed mechanism for SQL SERVER (tweaks and optimizations specific to SQL SERVER).ICache is a generic solution for all DataBase providers so IStorage performs better than ICache when back-end is SQL SERVER.
IStorage provides better resource locking/utilization mechanism (Multiple tables structure for resource bookmarking and locking).ICache mechanism uses single table for resource bookmarking.
IStorage guarantees multiple instance support.ICache doesn't guarantee multiple instance support.

Performance was significantly improved by replacing legacy ICache caching technique with IStorage caching technique which is preferred by Telerik Reporting due to its specific implementation for MS SQL Server as mentioned above.

Conclusion:

This solution improved the performance of Telerik report rendering process as well as provided support for multiple service instances deployment.

  • Facebook
  • Twitter
  • Tumblr
  • Pinterest
  • Google+
  • LinkedIn
  • E-Mail

Comments are closed.

SEARCH BLOG

Categories

  • Blog (490)
  • Captain's Log (1)
  • Closure Reports (45)
  • Experiments (7)
  • How-To (56)
  • Implementation Notes (148)
  • Learn More (156)
  • LMS (8)
  • Look Inside (10)
  • Operations Log (12)
  • Programmer Notes (20)
  • R&D (14)
  • Rescue Log (4)
  • Testimonials (25)
  • Uncategorized (4)

RECENT STORIES

  • GitHub Actions- Automate your software workflows with excellence
  • Yii Framework – Accomplish Repetitive & Iterative Projects with Ease
  • A Recipe for CRM Software Development
  • Are Agile and DevOps the same?
  • The Data Scientist’s Toolset

ARCHIVES

In Short

With the vteams model, you bypass the middleman and hire your own offshore engineers - they work exclusively for you. You pay a reasonable monthly wage and get the job done without hassles, re-negotiations, feature counts or budget overruns.

Goals for 2020

  • Open development center in Australia
  • Complete and Launch the Robot
  • Structural changes to better address Clients' needs

Contact Us

Address: NEXTWERK INC.
6790 Embarcadero Ln, Ste 100,
Carlsbad, CA 92011, USA

Tel: (858) 586 7777
Email: fahad@nextwerk.com
Web: www.vteams.com

© 2020 vteams. All Rights Reserved.

Content Protection by DMCA.com