Skip to main content
Tweeted twitter.com/StackTridion/status/1108337557815857153
deleted 6 characters in body
Source Link
Marko Milic
  • 8.9k
  • 3
  • 24
  • 60

We have started using bundles and one thing which I have noticed is that the whole bundle is processed (rendering etc.) only on one publisher. We have a fully scaled architecture with separate publisher and CM servers. So, earlier, when items were scheduled for publish at the same time, the load was distributed on all the publishers, but with bundles the whole bundle with all its items is processed on one publisher which effectively increases the time to publish by a simple multiplying factor (# of publishers).

  

For e.g., earlier if 24 pages took 2 minutes with 6 publishers, now it takes 12 minutes for the same number of pages (in a bundle) since they are all processed on the same publisher.

Question:

Is there a way to configure or has anyone got any solution or even a workaround to set the items to be distributed across the publishers, so that we can leverage the fully scaled publishing architecture (use all publishers)? This is definitely causing issues since the same # of pages which used to take x minutes for publish is now taking x * #of publishers minutes with the bundle feature.

With new features I am definitely not expecting a worst (if not better performance in any aspects in the tool), but this stands as an odd one out. I hope I am not wrong in my expectations!

We

We are on Tridion 2013 SP1.

We have started using bundles and one thing which I have noticed is that the whole bundle is processed (rendering etc.) only on one publisher. We have a fully scaled architecture with separate publisher and CM servers. So, earlier, when items were scheduled for publish at the same time, the load was distributed on all the publishers, but with bundles the whole bundle with all its items is processed on one publisher which effectively increases the time to publish by a simple multiplying factor (# of publishers).

  For e.g., earlier if 24 pages took 2 minutes with 6 publishers, now it takes 12 minutes for the same number of pages (in a bundle) since they are all processed on the same publisher.

Question:

Is there a way to configure or has anyone got any solution or even a workaround to set the items to be distributed across the publishers, so that we can leverage the fully scaled publishing architecture (use all publishers)? This is definitely causing issues since the same # of pages which used to take x minutes for publish is now taking x * #of publishers minutes with the bundle feature.

With new features I am definitely not expecting a worst (if not better performance in any aspects in the tool), but this stands as an odd one out. I hope I am not wrong in my expectations!

We are on Tridion 2013 SP1.

We have started using bundles and one thing which I have noticed is that the whole bundle is processed (rendering etc.) only on one publisher. We have a fully scaled architecture with separate publisher and CM servers. So, earlier, when items were scheduled for publish at the same time, the load was distributed on all the publishers, but with bundles the whole bundle with all its items is processed on one publisher which effectively increases the time to publish by a simple multiplying factor (# of publishers). 

For e.g., earlier if 24 pages took 2 minutes with 6 publishers, now it takes 12 minutes for the same number of pages (in a bundle) since they are all processed on the same publisher.

Question:

Is there a way to configure or has anyone got any solution or even a workaround to set the items to be distributed across the publishers, so that we can leverage the fully scaled publishing architecture (use all publishers)? This is definitely causing issues since the same # of pages which used to take x minutes for publish is now taking x * #of publishers minutes with the bundle feature.

With new features I am definitely not expecting a worst (if not better performance in any aspects in the tool), but this stands as an odd one out. I hope I am not wrong in my expectations!

We are on Tridion 2013 SP1.

edited tags
Link
David Forster
  • 8k
  • 2
  • 16
  • 29
Source Link
Vipin Kothari
  • 2.7k
  • 1
  • 11
  • 15

How to leverage fully scaled publishing architecture with bundles

We have started using bundles and one thing which I have noticed is that the whole bundle is processed (rendering etc.) only on one publisher. We have a fully scaled architecture with separate publisher and CM servers. So, earlier, when items were scheduled for publish at the same time, the load was distributed on all the publishers, but with bundles the whole bundle with all its items is processed on one publisher which effectively increases the time to publish by a simple multiplying factor (# of publishers).

For e.g., earlier if 24 pages took 2 minutes with 6 publishers, now it takes 12 minutes for the same number of pages (in a bundle) since they are all processed on the same publisher.

Question:

Is there a way to configure or has anyone got any solution or even a workaround to set the items to be distributed across the publishers, so that we can leverage the fully scaled publishing architecture (use all publishers)? This is definitely causing issues since the same # of pages which used to take x minutes for publish is now taking x * #of publishers minutes with the bundle feature.

With new features I am definitely not expecting a worst (if not better performance in any aspects in the tool), but this stands as an odd one out. I hope I am not wrong in my expectations!

We are on Tridion 2013 SP1.