Executing code often results in the Console just sitting there, with no red Stop sign (Using CTRL+ backtick I see 'console_input' as the likely culprit) and then finally it all executes at once really quickly (meaning the R code itself wasn't the slow part, and RStudio was preventing the executed code from actually getting to R).Using the File pane both for the first time and for general navigation is slow, and I get the spinning wheel a lot.Running the newest Rstudio daily build 1.2.862 right now.sluggishness of RStudio while working in Projects on a network drive. Here's a SO question where I illustrate the file system commands. I would not think this would be related, but I thought I'd mention it. Much more so than file system commands using the same machine. I'm not sure if this is related, but I've found that R's file commands, py for example are terribly slow across my network.

I recorded a screencast so you all can witness what I'm talking about: I've seen in old RStudio support periodic comments about RStudio being slow on a network connection, but nothing recently. I regularly open large files and copy/save across the wire with other applications. Note that my network drive is > 700 miles away but it's typically very usable. There is hardly any network traffic and typical blips of CPU usage. I've monitored CPU and also network traffic and nothing is getting pegged out. I have found that when I open an RStudio proj that's located on my corporate network, RStudio behaves very erratically and laggy.

Google drive desktop slow