Replies: 2 comments 3 replies
-
It might be helpful if you give a minimal example. It's possible some of the functions you're using are doing parallelization themselves. Can you post a minimal example? Additionally, if you use the sequential plan, can you confirm only one core is used? |
Beta Was this translation helpful? Give feedback.
-
@LeaLe88 , please see @scottkosty 's comment; that's the way forward to get to the bottom of your problem, which is not expected. Unrelated to your problem, please be aware that with: markers <- future_lapply(idents, function(x) {
Clu_marker <- FindMarkers(object = kid.filtered_new, ident.1 = x, test.use="poisson",latent.vars = "orig.ident")
Clu_marker$cluster <- x
},future.seed = TRUE) then markers <- future_lapply(idents, function(x) {
Clu_marker <- FindMarkers(object = kid.filtered_new, ident.1 = x, test.use="poisson",latent.vars = "orig.ident")
Clu_marker$cluster <- x
Clu_marker
},future.seed = TRUE) This is how R is designed, and has nothing to do with Futureverse or parallelization per se. |
Beta Was this translation helpful? Give feedback.
-
Dear all,
Following my previous post in Seurat github satijalab/seurat#8315 I have run below code in order to use multiple cores for the findmarkers function using the future package.
I was thinking this question now is more appropriate to post here in future github:
For some reason I am using all 64 cores even though I specified to use only 6:
BTW I had to add options(future.globals.maxSize = 8000 * 1024^2) in order to avoid the error shown above.
Do you know what could be the problem here?
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions