I posted this on the SAP Community forums, but have much better luck here. I am working on a sizing for a new BOBJ 4.3 SP1 install in which the content is primarily Crystal Reports.
Now the official sizing documentation is still based on 4.2 and in this, for the Crystal Reports 2016 processing server, there are calculations for the number of child processes that are spawned by the parent crystal process and the amount of memory these can consume. It is stated here that a child process can consume 500MB (1.25 per core) and the number of children are determined by the number of cores * 2.5. So with an 8 core system, the Crystal processing server supports 20 threads and consumes up to 10Gb.
Now this is all based on the 32-bit version of Crystal 2016 in 4.2 SP5+. In 4.3, the Crystal Reports 2020 Processing server is now 64-bit and doesn’t have the same memory constraint, theoretically 64-bit, but realistically like any of the other java components or 64-bit C++ components we configure. The closest we see in 4.2 is in the Crystal Enterprise Processing Server in which the child processes can consume up to 3GB of RAM and the number of children is calculated by cores / 2. So an 8 core system supports 4 enterprise threads and can consume up to 12GB of RAM.
I understand Crystal Enterprise is not the same as Crystal 2016 or 2020, BUT it is the closest 64-bit component to compare against. Since there is no memory constraint in the 64-bit version like the 32-bit version.
Does anyone know if there has there been any updated guidance on the sizing for the Crystal Reports 2020 processing server now that it is 64-bit?