Use https://packagemanager.rstudio.com to install R packages faster
#5220
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
harupy
changed the title
https://packagemanager.rstudio.com to install R packages faster
harupy
force-pushed
the
use-packagemanager-rstudio
branch
from
4b7afdb
to
97f56d2
Compare
Signed-off-by: harupy <hkawamura0130@gmail.com>
harupy
force-pushed
the
use-packagemanager-rstudio
branch
from
97f56d2
to
4442c92
Compare
Signed-off-by: harupy <hkawamura0130@gmail.com>
harupy
commented
Jan 5, 2022
mlflow/R/mlflow/.Rprofile
Outdated
Comment on lines
1
to
3
| # https://packagemanager.rstudio.com provides pre-compiled binary packages for Linux | ||
| # that can be installed significantly faster. | ||
| options(repos = c(REPO_NAME = "https://packagemanager.rstudio.com/cran/__linux__/focal/latest")) |
There was a problem hiding this comment.
The package installation (which usually takes 15~20 min) took 1.5 min with https://packagemanager.rstudio.com:
https://github.com/mlflow/mlflow/runs/4716557367?check_suite_focus=true#step:11:1
harupy
commented
Jan 5, 2022
Comment on lines
+98
to
+101
| working-directory: mlflow/R/mlflow | ||
| run: | | ||
| install.packages("devtools") | ||
| remotes::install_deps('mlflow/R/mlflow', dependencies = TRUE, upgrade = FALSE) | ||
| remotes::install_deps('.', dependencies = TRUE, upgrade = FALSE) |
There was a problem hiding this comment.
Run remotes::install_deps in mlflow/R/mlflow to allow R to find .Rprofile.
There was a problem hiding this comment.
where is .Rprofile file ?
There was a problem hiding this comment.
oh, in user home directory
Signed-off-by: harupy <hkawamura0130@gmail.com>
Signed-off-by: harupy <hkawamura0130@gmail.com>
|
nice 🥳 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes are proposed in this pull request?
Use https://packagemanager.rstudio.com to install R packages faster.
Before: 15 ~ 20 minutes
After: 1.5 minutes.
How is this patch tested?
Ensure the existing checks all pass.
Does this PR change the documentation?
ci/circleci: build_doccheck. If it's successful, proceed to thenext step, otherwise fix it.
Detailson the right to open the job page of CircleCI.Artifactstab.docs/build/html/index.html.Release Notes
Is this a user-facing change?
(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/artifacts: Artifact stores and artifact loggingarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesarea/examples: Example codearea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models: MLmodel format, model serialization/deserialization, flavorsarea/projects: MLproject format, project running backendsarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra: MLflow Tracking server backendarea/tracking: Tracking Service, tracking client APIs, autologgingInterface
area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows: Windows supportLanguage
language/r: R APIs and clientslanguage/java: Java APIs and clientslanguage/new: Proposals for new client languagesIntegrations
integrations/azure: Azure and Azure ML integrationsintegrations/sagemaker: SageMaker integrationsintegrations/databricks: Databricks integrationsHow should the PR be classified in the release notes? Choose one:
rn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notes