Our users started using Tridion bundles capability to club items which need to go together for time sensitive publishes. One of the challenges that we are facing with the usage of bundles is that it is very difficult to set a package size limit for the transport layer which sends the package to deployer via an https request. Currently, we have set the request size limit as 50MBs, but recently couple of bundles failed because they exceeded 50MBs. Increasing the request size limit is an option that I am not very positive on, since there isn't any limit to what the user can do. Also, short term I have recommended to use 10-15 items per bundle, but that restriction is causing lot of issues with the users since they have to create multiple bundles for a content release supposed to go together.
Is there a way to calculate the package size ahead of time so that we can let the users know that you cannot add anymore items to the bundle since it is going to fail at the publish time because of package size limit that is set.
I know that if we pre-render the package using advanced publish options or write event system code to trigger publish render on every item add to bundle, I can use filewatcher and capture the package to know the size. But, that seems a bit overkill since every time an item is added, I will have to trigger rendering. Is there an alternative way to find the package size. Has anybody faced a similar situation and what probable options are there for handling this scenario.
We are using Tridion 2013 SP1 and we have a fully scaled architecture, where we have separate CM and Publisher servers.