Depending on your exact needs, wouldn't a valid question be "
what is the MAX limit of #variables that can get a score 9 solution from the solution
in a given time limit"? Set a reasonable time limit and run your experiment in a binary search style - instead of just iterating through the range, do a more intelligent increase/decrease in the number of jobs/workers/what-have-you. For example, if you successfully get your score 9 in some run, then next double the number of "jobs", if that fails, then go to the halfway point between last successful and last unsuccessful. Note that you can stop early if you continuously evaluate the solutions and find a 7+ even if it's more difficult to evaluate than just your objective function.
But I think the consensus is that it's not just the number of variables/constraints that make a model difficult to solver. It's also the tightness of the constraints and variable bounds and what not. Small details can affect the runtime to a large extent.
Best,
Priidik