13

The LoadFlags differs a lot than say the ListBaseColumns enumeration, in that its actually a flag based property and not just a standard enum. While ListBaseColumns allows you to choose only ONE of the options, the LoadFlags lets you add mix and match by choosing one or many of the options. When you create a new ReadOptions(), the LoadFlags property is set ...


9

There are various optimization and checks you can do for performance in DXA Enable DD4T caching. <add key="CacheSettings_CallBackInterval" value="30" /> <add key="DD4T.CacheSettings.Page" value="3600" /> <add key="DD4T.CacheSettings.Component" value="3600" /> Outputcaching as you mentioned. Make sure your binaries css, images, and js are ...


9

Doesn't Content Service become bottleneck on SDL Web 8.5? Yes and no. You're indeed in fact moving the processes, libraries and dependencies which fetch data from the Broker DB from the web app to a separate server or service. The effect of this is, that processes surrounding requests are spread across different JVMs, which in total bring a more scalable ...


7

I have contacted Fredhopper customer support and they have provided me with the scripts: log-analyzer.pl and log-analyzer.py. If you have the similar request, please feel free to contact them and they should provide it to you.


6

You enable Tridion caching by updating your Storage Configuration, as shown below <ObjectCache Enabled="true"> <Policy Type="LRU" Class="com.tridion.cache.LRUPolicy"> <Param Name="MemSize" Value="16mb"/> </Policy> <Features> <Feature Type="DependencyTracker" Class="com.tridion.cache.DependencyTracker"/> &...


6

Brilliant response from Alex, to answer your question from another angle though; you can avoid constantly passing a new instance by declaring a number of static instances. Review the use cases where you're accessing Core Service and what levels of data you're likely to need back. Then classify those data levels for easy access and maintenance. For example:...


5

This isn't just your concern, this topic was discussed a lot when the change in architecture was suggested. Now while all (architecture) changes will have their pros and cons, once the decision was made to change the Content Delivery architecture from in-process to micro services, the cons of this change have all been mitigated. For example, a lot of ...


4

This is a great question. We’ve had initial performance concerns (problems!) with the Content Service on a couple of projects that I’ve worked on. These have manifested in high CPU usage mainly. However, we have managed to mitigate these by: Using a good caching strategy (Tridion object cache, CIL caching and caching in the Web app) Making sure the latest ...


4

I don't see that the ComponentPresentationFactory has any methods which accept an array of component IDs that would return you multiple ComponentPresentations. There are two methods which accept a Keyword or Keywords which could possibly be used if you are classifying your news components? Many implementations do this kind of querying for multiple pieces of ...


4

i think your are loading too much content from the broker. Can't you do just some optimization. As mentioned by @Tanner Object Cache with CCS is indeed very good option check if it helps Nothing works better than optimizing your queries. how about putting some taxonomy and find only required content at load then lazy load rest of it. Keep your db indices ...


4

@Shatadru, How you are invalidating your application level cached result to reflect published data? To improve the performance of you query execution you can check the below options: Broker database maintenance(You can check the link) Broker query optimization- We can directly relate broker query with the SQL query being executed on broker database and ...


3

By design ECL will refresh thumbnails when either: The etag change The version of the ECL provider change I can't remember if it will also regenerate when the version of ECL (so Tridion) changes. Typically I would expect this behavior if the etag is not calculated identically each time. To verify it, identify a cached thumbnail to check. Rename it to old....


3

You may try following option: Keep the Maintenance Plan for SDL Tridion in effect and quite frequent - for extensive broker queries, I guess it was recommended to run the SDL Tridion Maintenance Plan every day, twice a day or even every few hours depending on the number of transactions and in parallel optimize the Broker Query as much possible - Check the ...


3

It absolutely depends on what you are trying to achieve. If your components are going to be in millions, then it makes sense that you use the Broker Database and use Broker API (for Tridion 2009 and below) or Content Delivery Web Service (for Tridion 2011 and above). The reason is that it may become a problem if millions of files in the size of several Giga ...


3

This is weird and we don't see this effect in our DXA Load Test (which we run nightly); we get total response times (Page + embedded resources like images) of approx. 50 ms, so not more than a few ms per image. I do notice that you have the ADF Module enabled and ADF is known to cause significant performance overhead. If you don't use ADF (i.e. you have a ...


2

I've encountered a similar issue at a client where there were a lot of groups and a lot of publications. When logging into the CM, if a regular user it would take 15 minutes to log in, but admins would be instant. The issue was due to how the CM checks which group a user belongs to and what publications and folders he has access to. It's basically a very ...


2

It's not an easy question to answer. In general, I would say that you will run into usability issues with the volumes long before you run into performance issues. The one possible exception might be the claims, since they are in memory on your web server. So you'll want to be a little thoughtful about the amount of data that you put in claims. But if you ...


2

My preference for data distribution is always to use the database, but not necessarily for caching reasons. While, yes, caching will help (btw, we will also cache Component Presentations stored in the File System), the single biggest advantage in my view is one of data consistency across servers. When using a single server for Content Delivery, data ...


2

This limited mostly by how big of a request TMS API can handle. Translation Manager send all files in one request so if it is not split, at some point TMS API will fail with timeout or something. Another consideration, is that with big amount of tasks in one job, TMS UI can become unwieldy for people who work on TMS side. Also, if customer uses out-scaled ...


1

I asked SDL support about this issue, and new Hotfix TM_8.5.0.11182 was provided.The Hotfix solved this problem.


1

I agree with Raj, that you are loading too much of data for the first time. For, Caching implementation you can check from here also along with the other references from Tanner. Now from your question, it seems you don't have to load all of the data(forms) for any specific user. Firstly, I don't think loading the data at Application_Start will solve your ...


Only top voted, non community-wiki answers of a minimum length are eligible