I had asked this in the “General” forum, but that was likely not the best forum
Achilles on Postgres — analysis 117 extremely slow, Query drops silently, numThreads fails - #2 by schuemie
Issue:
For our large OMOP, Achilles run from the R code is failing for us - long queries in our postgres database
My question:
It is my understanding that we can do this:
- Run Achilles with the “sqlonly” parameter that will generate all achilles.sql for our database type (postgres)
- We can then simply run that entire set of sql commands independent of the R packages and end with the same final results into 2 files: achilles_results_dist, and achilles_results
Is that correct?
This way we can manipulate and enhance the performance of the resulting Postgres queries.
The SqlRender() version for postgres are often not efficient, especially for CONDITION_OCCURRENCE table with 859 million rows and a MEASUREMENT table with 5.3 billion rows
Thanks, Jeff