@slopp, assuming I want to be as close to scenario B (as described in the tuning and scaling document) as possible, what is the better setting for the utilization scheduler.
Option 1
utilization_scheduler 1 0.5 15
Option 2
utilization_scheduler 1 0.9 40
Maybe a brief description of my app would be helpful also. I have an app that loads very quickly since it loads only code. The app allows a user to read in a very large file and do some work on it, and this can take up to 20 - 30 minutes.
So, ideally, I want each user to access the URL we created where the app lives and essentially have their own R process and session and in no way collide with work any other user might be doing. We previously had this app set up where it ran locally on each person's machine, so there was never any competing for resources between different users.
I would like to come as close as possible to that type of usage as possible if that makes sense.
Thank you for your advice
Harold