You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2021/03/19 08:51:25 UTC
[GitHub] [openwhisk] coderofsalvation opened a new issue #5094: what is a normal response time for hello world? [openwhisk standalone]
coderofsalvation opened a new issue #5094:
URL: https://github.com/apache/openwhisk/issues/5094
## Environment details:
* local deployment
* docker 18.09.8-ce, alpine linux 3.10
## Steps to reproduce the issue:
```bash
$ AUTH=$(docker exec openwhisk wsk property get --auth | awk '{ print $3 }' )
$ wsk property set --auth $AUTH --apihost http://localhost:3233
$ echo 'function main(args) {
const name = args && args.name || "stranger";
return { greeting: `Hello ${name}!` };
}' > hello.js
$ wsk action create helloJS hello.js --concurrency 10
error: Unable to create action 'helloJS': The request content was malformed:
requirement failed: concurrency 10 exceeds allowed threshold of 1 (code oUwMJCOQ4NCcatFSX49kTCwaFYtxhX7D)
Run 'wsk --help' for usage.
$ wsk action create helloJS hello.js
ok: created action helloJS
$ time curl -H 'Content-Type: application/json' -X POST -u "$AUTH" http://localhost:3233/api/v1/namespaces/guest/actions/helloJS?blocking=true
$ time curl -H 'Content-Type: application/json' -X POST -u "$AUTH" http://localhost:3233/api/v1/namespaces/guest/actions/helloJS?blocking=true
{....,"response":{"result":{"greeting":"Hello ${name}!"}...}
real 0m1.031s
user 0m0.005s
sys 0m0.001s
$ time curl -H 'Content-Type: application/json' -X POST -u "$AUTH" http://localhost:3233/api/v1/namespaces/guest/actions/helloJS?blocking=true
{....,"response":{"result":{"greeting":"Hello ${name}!"}...}
real 0m0.501s
user 0m0.004s
sys 0m0.001s
```
## Provide the expected results and outputs:
I expected the second curl response-time to be much smaller/faster.
## Provide the actual results and outputs:
* Why is concurrency limited 1 for to nodejs:10? Documentation states otherwise.
* It seems that, the more time is in between the curl calls..the smaller/faster the responsetime is.
Given a fair amount of activations, I would expect any recurring call to be superfast:
```
$ wsk activation list | grep helloJS | grep warm | wc -l
27
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] coderofsalvation edited a comment on issue #5094: normal nodejs response time/concurrency for hello world? [specifically for openwhisk standalone]
Posted by GitBox <gi...@apache.org>.
coderofsalvation edited a comment on issue #5094:
URL: https://github.com/apache/openwhisk/issues/5094#issuecomment-817602058
I've modified the title to emphasize the initial spirit of my question (how to achieve this with the provided standalone docker-image). Here a bit more background:
> REASON: the standalone image makes it deadsimple to try/develop openwhisk locally across teams. However, tweaking a docker-image to make it support nodejs's default concurrent behaviour is not deadsimple.
So maybe in this spirit, this can also be seen as a request for a **docker-flag** or **default nodejs concurrency** for the standalone image to boost the adoption from the nodejs-community / newcomers.
Otherwise it's very hard to convince nodejs-developers to choose something like OpenWhisk over OpenFaaS, when nodejs-concurrency is practically disabled by default.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] coderofsalvation edited a comment on issue #5094: normal nodejs response time/concurrency for hello world? [specifically for openwhisk standalone]
Posted by GitBox <gi...@apache.org>.
coderofsalvation edited a comment on issue #5094:
URL: https://github.com/apache/openwhisk/issues/5094#issuecomment-817602058
I've modified the title to emphasize the initial spirit of my question (how to achieve this with the provided standalone docker-image). Here a bit more background:
> REASON: the standalone image makes it deadsimple to try/develop openwhisk locally across teams. However, tweaking a docker-image to make it support nodejs's default concurrent behaviour is not deadsimple.
So maybe in this spirit, this can also be seen as a **docker-flag request** for the standalone image to boost the adoption from the nodejs-community / newcomers.
Otherwise it's very hrd to convince nodejs-developers to choose something like OpenWhisk over OpenFaaS, when nodejs-concurrency is practically disabled by default.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] rabbah commented on issue #5094: what is a normal response time for hello world? [openwhisk standalone]
Posted by GitBox <gi...@apache.org>.
rabbah commented on issue #5094:
URL: https://github.com/apache/openwhisk/issues/5094#issuecomment-803370642
> Why is concurrency limited 1 for to nodejs:10
The default is limit. You can change this for your deployment.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] davidfrickert commented on issue #5094: what is a normal response time for hello world? [openwhisk standalone]
Posted by GitBox <gi...@apache.org>.
davidfrickert commented on issue #5094:
URL: https://github.com/apache/openwhisk/issues/5094#issuecomment-812935010
I'm also interested in a guide on how to change concurrency limits. Is this a limit on the deployment on the action?
https://github.com/apache/openwhisk/blob/master/docs/concurrency.md says nothing about this.
Even googling for this error leads to nowhere.
I'm using a custom https://github.com/apache/openwhisk-devtools Makefile to deploy 1.0.0 openwhisk locally.
@rabbah can you share some insight please?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] coderofsalvation edited a comment on issue #5094: normal nodejs response time/concurrency for hello world? [specifically for openwhisk standalone]
Posted by GitBox <gi...@apache.org>.
coderofsalvation edited a comment on issue #5094:
URL: https://github.com/apache/openwhisk/issues/5094#issuecomment-817602058
I've modified the title to emphasize the initial spirit of my question (how to achieve this with the provided standalone docker-image). Here a bit more background:
> REASON: the standalone image makes it deadsimple to try/develop openwhisk locally across teams. However, tweaking a docker-image to make it support nodejs's default concurrent behaviour is not deadsimple.
So maybe in this spirit, this can also be seen as a **docker-flag request** for the standalone image to boost the adoption from the nodejs-community / newcomers.
Otherwise it's very hard to convince nodejs-developers to choose something like OpenWhisk over OpenFaaS, when nodejs-concurrency is practically disabled by default.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] rabbah commented on issue #5094: normal nodejs response time/concurrency for hello world? [specifically for openwhisk standalone]
Posted by GitBox <gi...@apache.org>.
rabbah commented on issue #5094:
URL: https://github.com/apache/openwhisk/issues/5094#issuecomment-817733050
Thanks for clarifying the issue further 👍
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] coderofsalvation edited a comment on issue #5094: normal nodejs response time/concurrency for hello world? [specifically for openwhisk standalone]
Posted by GitBox <gi...@apache.org>.
coderofsalvation edited a comment on issue #5094:
URL: https://github.com/apache/openwhisk/issues/5094#issuecomment-817602058
I've modified the title to emphasize the initial spirit of my question (how to achieve this with the provided standalone docker-image). Here a bit more background:
> REASON: the standalone image makes it deadsimple to try/develop openwhisk locally across teams. However, tweaking a docker-image to make it support nodejs's default concurrent behaviour is not deadsimple.
So maybe in this spirit, this can also be seen as a **docker-flag request** for the standalone image to boost the adoption from the nodejs-community / newcomers.
It's a hard sell to convince nodejs-developers to choose something like OpenWhisk over OpenFaaS, when nodejs-concurrency is not the default.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] rabbah commented on issue #5094: what is a normal response time for hello world? [openwhisk standalone]
Posted by GitBox <gi...@apache.org>.
rabbah commented on issue #5094:
URL: https://github.com/apache/openwhisk/issues/5094#issuecomment-817317114
@tysonnorris might be better at answering this. I can look into it otherwise.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] rabbah commented on issue #5094: what is a normal response time for hello world? [openwhisk standalone]
Posted by GitBox <gi...@apache.org>.
rabbah commented on issue #5094:
URL: https://github.com/apache/openwhisk/issues/5094#issuecomment-817318103
This should be closed as a duplicate of https://github.com/apache/openwhisk/issues/4811.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] coderofsalvation commented on issue #5094: what is a normal response time for hello world? [specifically for openwhisk standalone]
Posted by GitBox <gi...@apache.org>.
coderofsalvation commented on issue #5094:
URL: https://github.com/apache/openwhisk/issues/5094#issuecomment-817602058
I've added the 'specifically' word in the topic of this issue, to emphasize the spirit of my question (how to achieve this with the provided standalone docker-image).
> REASON: the standalone image makes it deadsimple to try/develop openwhisk locally across teams. However, tweaking a docker-image to make it support nodejs's default concurrent behaviour is not deadsimple.
So maybe in this spirit, this can also be seen as a **docker-flag request** for the standalone image to boost the adoption from the nodejs-community / newcomers.
It's a hard sell to convince nodejs-developers to choose something like OpenWhisk over OpenFaaS, when nodejs-concurrency is not the default.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] coderofsalvation commented on issue #5094: what is a normal response time for hello world? [openwhisk standalone]
Posted by GitBox <gi...@apache.org>.
coderofsalvation commented on issue #5094:
URL: https://github.com/apache/openwhisk/issues/5094#issuecomment-803373822
> The default is 1. You can change this for your deployment.
Right, so above you can see im trying to change it.
How would one do that given the above standalone installation?
On Sat, Mar 20, 2021, 3:59 PM rodric rabbah ***@***.***>
wrote:
> Why is concurrency limited 1 for to nodejs:10
>
> The default is 1. You can change this for your deployment.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/openwhisk/issues/5094#issuecomment-803370642>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AABL6ZADLUB22G4DQ67TDFTTESZ6PANCNFSM4ZOLIQJQ>
> .
>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] rabbah edited a comment on issue #5094: what is a normal response time for hello world? [openwhisk standalone]
Posted by GitBox <gi...@apache.org>.
rabbah edited a comment on issue #5094:
URL: https://github.com/apache/openwhisk/issues/5094#issuecomment-803370642
> Why is concurrency limited 1 for to nodejs:10
The default is 1. You can change this for your deployment.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org