Systembuilder is a very different animal than plain Simpl. It's running the full suite of Crestron programs at the same time but it's also running Axis and lord knows what else beneath the hood to link the database to those Cresetron apps and generating the actual programs the hardware requires to work. It's not a single smw file.

I'm doubtful that a cpu test based on Simpl tells you very much about using Systembuilder. Systembuilder is not just compiling a simpl Windows program. It's building the graphics files and code from these databases. It's linking the changes you've made to the underlying databases and linking those to templates upon which the source code for a project is being generated. You are compiling source code. Systembuilder is generating the source code from the underlying databases.


It seems logical therefore that Systembuilder will place greater demands on a computer than Simpl Windows or VT-Pro by themselves. The basic database in Axis has to be stitched into these other programs, where templates build the basic UI and then the logic in each and every UI has to be woven.

In evaluating the correct CPU for this application you do need to provide a test for a program that is going to run multiple, related applications and other applications that link and stitch these applications together. You may still be correct but, logically, you seem to be testing something very different from Systembuilder and making a conclusion that doesn't seem to relate to it.

Alan