Posted: 19 May 2017 8:31 EDT Last activity: 23 Aug 2018 19:06 EDT
Approximation of deployment artefact size
To help with some non-functionals i need to approximate the size of a robotic solution deployable. Our organisation does not have existing artefacts to base this approximation on and i do not know how efficient the compilation of a robotic artefact is.
So for example what would the size be for:
A solution that is made up of 60 projects, each project has a process with 20 steps in it.
I am fully aware that there will be other impacting factors but i am hoping that this is enough to say ballpark that a deployable is
a. < 500KB
Could anyone use their experience to approximate this or maybe pose any further questions so that an approximation would be possible?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
The simple answer to this that it all depends on how it is programmed. Realistically, you would never have 60 projects in a solution and you would also write automations that promoted reuse. Some of the largest projects I have ever seen could be between 5 - 10 mb when deployed, but most are smaller than that. It depends on so many other factors as well such as are you adding your own assemblies which must be deployed with the project?