Marcin Copik

@RomanSpies @fwsGonzo I found that there is already internal support for using `string_view` as the response body. However, it is used in a private method of the `HttpResponse` class through...

@octonawish-akcodes Thanks for the PR! What would be needed to add later a Python version?

@nervermore2 > Google Cloud published Google Cloud Function V2 last year, which is built on Cloud Run and Eventarc. It is interesting to see it's performance under Sebs benchmark set....

@nervermore2 > Also, wondering if it's possible to support Python 3.8+ on GCP. It seems like the image we are using only supports python 3.7, however, if choose other images...

@nervermore2 Thanks for the detailed information - yes, the building of Docker images is a deeply internal part that is not documented very well. Users are not expected to know...

@nervermore2 > Thanks, it would be great helpful if we can have both new Node.js images (16.x or even higher) and also new python images (3.8x or even higher) for...

@nervermore2 On the `dev` branch and in DockerHub, you can find GCP images for Python 3.7, 3.8, and 3.9. This required some major changes to our images. Furthermore, the benchmark...

> So we install dependencies in the docker, and ship them (may be in a dockerized image or zipped file) along with the code right. That's why we see requirements.txt...

@nervermore2 You can find support for Node 16 on `dev` branch and in our DockerHub. Updating to Node.js 18 might be possible - we will explore later if the existing...

@nervermore2 > Thanks! It seems like since we are only importing libraries and then run benchmarks, adding stuff to requirements.txt could be enough for the dependencies. But apparently, you did...