You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Render .Rmd file in Rstudio in a repository with git set-up on Windows machine with enterprise security software Avecto Defendpoint.
Describe the problem in detail
On my Windows work computer, in Rstudio Desktop, after knitting documents, projects with git are EXTREMELY slow to open the Rstudio preview browser. Rstudio seems to be affected more than the underlying R process. For example, when I check the folder (with Windows File Explorer), I will see the files have successfully rendered and I can open them with Chrome, etc. even though the RStudio preview browser will still not successfully display the rendered file for a few minutes. Rstudio performance, in general, often becomes significantly degraded (e.g. "Files" pane is slow updating and I'll find saving files, opening new files, etc. becomes unresponse or highly delayed).
When encountring this I've also noticed our enterprise security software Avecto Defendpoint becomes hyperactive in its CPU usage (I checked this using "task manager").
These issues do not show-up when knitting identical files on non-git respositories. For repositories that do have git, if I disable Rstudio's git interface (but keep git on the respoitory) the issue also goes away ("Tools" --> "Global Options" --> "git/svn" --> deselect "Enable verson control for Rstudio projects"; disabling on just the project also fixes the problem).
Here is an example file I've used to test this behavior. If I knit this file in a repo with git, Rstudio is extremely slow whereas if I run it in a repo without git (or disable Rstudio's git interface) it seems to run normally.
I first referenced this on this thread (sorry to @kevinushey for the slowness in creating a new issue as recommended). I've seen some threads on Rstudio community and elsewhere that I thought might be a related problem (e.g. here). Though, outside of localizing this to some kind of git-Avecto-Rstudio interaction, I'm not sure what is going on.
Let me know if there is other information I should provide, or things you recommend I try (my current action has been to usually disable Rstudio's git interface). I've also opened a ticket with our IT and they've opened a ticket with Avecto (so if there are notes/actions I should forward their way -- and require admin access -- please let me know).
The text was updated successfully, but these errors were encountered:
One other thing worth confirming: is the .git folder in your project directories hidden or not? (I recall that a previous version of this issue was resolved if the user made sure to re-hide the .git folder, as it had somehow lost that attribute)
I had also logged a ticket with our internal IT support team who forwarded the issue to BeyondTrust. They ultimately came back with the following response:
BeyondTrust support has exhausted all options to improve the CPU utilization of the Defendpoint service, the company policy and Git/RStudio. The improvements we worked on with them are active in the production policy today.
The Rstudio/Git combination sends hundreds or thousands of processes into the Defendpoint service, which unfortunately cannot process that much that rapidly. This is why we still see the delay in rendering the R documents even with a blank policy.
At this point we have no next steps as far as troubleshooting. I'd like to resolve the ticket as...
Note that the issue is more with the RStudio browser not opening and RStudio becoming slow / unresponsive (the file itself may render -- and could be opened from Chrome etc. -- but will not display in the Rstudio browser for maybe a couple minutes and other RStudio functionality also seems to slow down).
System details
Created on 2019-05-24 by the reprex package (v0.2.1)
Steps to reproduce the problem
Render .Rmd file in Rstudio in a repository with git set-up on Windows machine with enterprise security software Avecto Defendpoint.
Describe the problem in detail
On my Windows work computer, in Rstudio Desktop, after knitting documents, projects with git are EXTREMELY slow to open the Rstudio preview browser. Rstudio seems to be affected more than the underlying R process. For example, when I check the folder (with Windows File Explorer), I will see the files have successfully rendered and I can open them with Chrome, etc. even though the RStudio preview browser will still not successfully display the rendered file for a few minutes. Rstudio performance, in general, often becomes significantly degraded (e.g. "Files" pane is slow updating and I'll find saving files, opening new files, etc. becomes unresponse or highly delayed).
When encountring this I've also noticed our enterprise security software Avecto Defendpoint becomes hyperactive in its CPU usage (I checked this using "task manager").
These issues do not show-up when knitting identical files on non-git respositories. For repositories that do have git, if I disable Rstudio's git interface (but keep git on the respoitory) the issue also goes away ("Tools" --> "Global Options" --> "git/svn" --> deselect "Enable verson control for Rstudio projects"; disabling on just the project also fixes the problem).
Here is an example file I've used to test this behavior. If I knit this file in a repo with git, Rstudio is extremely slow whereas if I run it in a repo without git (or disable Rstudio's git interface) it seems to run normally.
I first referenced this on this thread (sorry to @kevinushey for the slowness in creating a new issue as recommended). I've seen some threads on Rstudio community and elsewhere that I thought might be a related problem (e.g. here). Though, outside of localizing this to some kind of git-Avecto-Rstudio interaction, I'm not sure what is going on.
Let me know if there is other information I should provide, or things you recommend I try (my current action has been to usually disable Rstudio's git interface). I've also opened a ticket with our IT and they've opened a ticket with Avecto (so if there are notes/actions I should forward their way -- and require admin access -- please let me know).
The text was updated successfully, but these errors were encountered: