Skip to main content

Toolkit - Performance

Image
By
This post if part of a series about the File System Toolkit - a custom content delivery API for SDL Tridion.

This post presents performance data that was captured for each major functionality with and without caching Linking, CP Assembler, Component Presentation Factory, Dynamic Content Queries, Model Factory.

The data was captured on a 2014 Macbook Pro 15", 16 GB RAM, 2.6 GHz Intel Core i7 running OS X El Capitan.

Test methodology: each test was run for 3 minutes and the total number of successful Toolkit API calls was measured. Then the number of calls per second was computed 'with cache' and 'without cache' test runs. Then a cache boost factor was calculated by diving (the number of API calls with cache) / (number of API calls without cache).

Each cache test was executed 3 times, with different cache time-to-live values of 1 second, 5 seconds and 0 seconds (eternal cache, no expiration). The rationale is to see what impact different cache expiration/eviction values have on the overall performance.

Then finally the entire suite of tests was run twice in order to calculate averages.

Model Factory

Only read model operations were calculated. The reasoning is that Deployer extension is the only one that creates / writes the JSON files and as such that operation is much less frequent than read operations that are used all the time during the normal functioning of the Toolkit.

Models read per second: 1.9m (with cache) and 26k (without cache)
Cache boost: 73x

Model Factory read performance


Link Factory

The test executed component, page and binary links. Each LinkFactory method was executed and counts as one API call.

Links resolved per second: 383k (with cache) and 26k (without cache)
Cache boost: 15x

Link Factory resolve performance


Component Presentation Factory

The test executed getComponentPresentation and getComponentPresentationWithHighestPriority factory calls. Each call counts as one API call. Each factory calls makes one ModelFactory read call, so the times below include also the ModelFactory call duration.

CPFactory calls per second: 3.2m (with cache) and 24k (without cache)
Cache boost: 135x

Component Presentation Factory read performance

Component Presentation Assembler

The test executes a getComponentPresentation factory method which counts as one API call. The call includes a CPFactory call, so the times below include also the CPFactory call duration.

CPAssembler calls per second: 55k (with cache) and 17k (without cache)
Cache boost: 3x

Component Presentation Assembler performance

Dynamic Content Query

The dynamic content queries are not cached. Therefore, the times below are pretty much the same. The tests were executed using different combinations of query criteria (custom meta, schema, date ranges, pagination, and vs or complex queries). Each query counted as one API call. The numbers below represent an average duration of each of these queries. No models were created during the dynamic queries, the queries simply returned the TcmUri of the identified items.

Dynamic queries per second: 6.8k

Dynamic Query performance


Labels:

Comments

Post a Comment

Popular posts from this blog

Running sp_updatestats on AWS RDS database

By
Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as...
2 comments
Read more

REL Standard Tag Library

By
The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...
2 comments
Read more

Publish Binaries to Mapped Structure Groups

By Unknown
Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to a...
10 comments
Read more