I have been testing small api requests (hosted on aws, docker, germany) and requests are pretty fast, 20-30ms.
Is this comparable to django rest api?
Hi again,
I started to use the tool more extensively, everything is great so far.
Just talked to a friend and he shared me this
https://github.com/the-benchmarker/web-frameworks
where restrserve (0.3) is quite behind vs other frameworks.
Are these numbers accurate overall?
I will never have more than 50-100 requests per second but just curious if R is this behind the other frameworks?
On the other side when you do some useful computations (if you spend at least 1-5 ms to compute something) such benchmarks don't make much sense and platforms above will perform similarly.
I would say yes. You can see pure Rserve does ~42k req/seq but it's barebone - you need to implement input validations, exception handling, etc. Which in interpreted language like R takes some time.
On the other side when you do some useful computations (if you spend at least 1-5 ms to compute something) such benchmarks don't make much sense and platforms above will perform similarly.
Thanks for the reply.
WORKDIR /
EXPOSE 8080
CMD ["Rscript", "-e", "source('/home/ubuntu/nqr_r_backend/app.R'); backend$start(app, http_port = 8080)"]FROM rocker/tidyverse
RUN install2.r --error RestRserve
RUN install2.r --error Quandl
RUN install2.r --error PerformanceAnalytics
RUN install2.r --error xts
RUN install2.r --error quantmod
COPY / /
EXPOSE 8080
ENTRYPOINT ["Rscript", "app.R"].res$set_content_type("application/json")
.res$set_body(output) is already a JSON, it kind of wraps it one more time into JSON.
Another question, my front-end colleague gets this message when fetching from api using JS
Access to XMLHttpRequest at 'api_url'
from origin 'http://localhost:8080' has been blocked by CORS policy: No 'Access-Control-Allow-Origin'
header is present on the requested resourceHi @dselivanov
I was able to succesfully test CORS with plain text and GET.
However I am not able to have work with JSON. If I do this
app$add_route("/bth", method = "OPTIONS", FUN = function(req, res) {
res$set_header("Allow", "GET, OPTIONS")
})And in my function I have
results = data.frame(x = 123)
.res$set_body(results)
.res$set_content_type("application/json")I receive "500 Internal Server Error (body is not character or raw)"
if (isTRUE(is.raw(body) || is.character(body))) {
return(list(body, response$content_type, headers, response$status_code))
} else {
return(list("500 Internal Server Error (body is not character or raw)", "text/plain", headers, 500L))
}raw output - REST clients can only read bytes and interpret as per coupled MIME code. So you need to encode your R object response into bytes. RestRserve tries to do so automagically for application/json, but for other types you need to do it yourself.
exec('Rscript -e mysscript.R', $output, $result) see https://stackoverflow.com/a/53172260/4530144)
$result = $client->post('http://localhost:12345/myRscript', ['parameter', 'some value']) and get back a (JSON or HTML) string as a result
There is an example on the very first paragraph of the readme.
library(RestRserve)
app = Application$new()
app$add_get(
path = "/health",
FUN = function(.req, .res) {
.res$set_body("OK")
})
app$add_post(
path = "/addone",
FUN = function(.req, .res) {
result = list(x = .req$body$x + 1L)
.res$set_content_type("application/json")
.res$set_body(result)
})
backend = BackendRserve$new()
backend$start(app, http_port = 8080)Why it doesn't work for you?