aboutsummaryrefslogtreecommitdiff
path: root/doc/rpy2-performance.org
diff options
context:
space:
mode:
authorBonfaceKilz2021-06-17 10:20:39 +0300
committerBonfaceKilz2021-06-17 10:24:50 +0300
commita5981b8e71380b171b210d55da58e5037b455a6c (patch)
tree32c632cbae4e1e2232d31e423b62760c543cabc1 /doc/rpy2-performance.org
parenta992e2038424c2acdf11078356204847d128c8c6 (diff)
downloadgenenetwork2-a5981b8e71380b171b210d55da58e5037b455a6c.tar.gz
doc: rpy2-performance: Add a section exploring possible solutions
Diffstat (limited to 'doc/rpy2-performance.org')
-rw-r--r--doc/rpy2-performance.org9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/rpy2-performance.org b/doc/rpy2-performance.org
index 177c427e..8f917ca0 100644
--- a/doc/rpy2-performance.org
+++ b/doc/rpy2-performance.org
@@ -171,3 +171,12 @@ from locust import HttpUser, task, between
self.client.get("/test")
#+end_src
+
+** A possible solution
+
+From this [[https://github.com/rpy2/rpy2/issues/809#issuecomment-845923975][comment]], a possible reason for the above traces, is that
+from Flask's end, a [[https://tldp.org/LDP/lpg/node20.html][SIGPIPE]] is somehow generated by our Python
+code. However, at this particular point, the R thread just happens to
+be running, and R can't handle this correctly. This seems to have been
+fixed in this [[https://github.com/rpy2/rpy2/pull/810][PR]] with a this [[https://github.com/rpy2/rpy2/issues/809#issuecomment-851618215][explanation]]. On our end, to have these
+changes, we have to update our python-rpy2 version.