Hi @tkmamidi, indeed the n_jobs=-1 would allow as many concurrent trials as you have resources available. This obviously depends on your cluster setup, but assuming you are running on a cluster in which 200 trials can be run concurrently, all of them will run at the same time.
In that case, yes, the search optimization is pretty meaningless as all configurations will be sampled at the start of the run and the search algorithm has no additional information to make better guesses.
Thus you may want to limit the number of jobs running in parallel. Depending on your problem, 50 seems fine, though you could also start with 20 or so. Just know that this will obviously impact training time.
By the way, even if you are resource constrained by your cluster, you should still set n_jobs to some number as even if trials cannot be run concurrently, configurations will still be started at the start of the run.