Closed hadley closed 2 years ago
I haven't changed anything, but Microsoft365R isn't that optimised. The server could also just be slow right now.
Does profiling show any obvious bottlenecks?
i'm having the same problem. When a try to pin some large DT i'm having the error:
"Error in curl::curl_fetch_memory(url, handle = handle) : OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 104"
I can't pin large datasets.
@lemuelemos that's not the same problem. Please create a reprex and file a new issue.
I ran a profile on test-board_ms365.R
, and it took ~5 minutes to run the MS365 check. It looks like 90% of the time is spent waiting for the server:
r$> summaryRprof("~/misc/pins_profile.out")
$by.self
self.time self.pct total.time total.pct
"curl::curl_fetch_memory" 298 90.85 298 90.85
"curl::curl_fetch_disk" 27 8.23 27 8.23
"cat" 1 0.30 1 0.30
"sub" 1 0.30 1 0.30
"validate" 1 0.30 1 0.30
I can have a look at whether there are any API calls that can be stripped out.
I also found a bug in board_ms365_test_driveitem
which I'll make a PR for.
The detailed profile output. Nothing really stands out....
Hmmm, maybe we should switch to smaller data files? I'm going to be working on pins again this week, so I'll hopefully have refamiliarised myself with what's going on shortly.
Looks like there's nothing obvious we can do to improve performance so I'm going to close this. If I get too annoyed by how long it takes these tests to run, I might add some skip functionality based on an env var.
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.
They're taking > 80s for me. @hongooi73 did anything change lately? I don't remember them being this slow when I last worked on pins.