CPU spike when using feathers socketio
When I make load test using Artillery to my feathers app that uses socketio as transport the CPU spikes to 100% and more. my production environment is digital ocean droplet with 2 CPU cores and 4GB of RAM. My test script is:
config:
target: "http://104.248.160.95:3030"
engine: 'socketio'
phases:
- duration: 10
arrivalRate: 20
defaults:
headers:
from: 'header'
processor: "./shi_users_generator.js"
scenarios:
- name: "Authenticating a user"
flow:
# call getUser() to create the name, email, and password variables
- function: "getUser"
- post:
url: "/authentication"
json:
strategy: "local"
email: "{{ email }}"
password: "{{ password }}"
# Print the data we're sending while debugging the script:
- log: "Sent a request to /authentication with {{ email }}, {{ password }}"
there is a file called shi_users_generator.js in the same directory with the test and has a method called getUser
node.js socket.io load-testing cpu-usage feathersjs
add a comment |
When I make load test using Artillery to my feathers app that uses socketio as transport the CPU spikes to 100% and more. my production environment is digital ocean droplet with 2 CPU cores and 4GB of RAM. My test script is:
config:
target: "http://104.248.160.95:3030"
engine: 'socketio'
phases:
- duration: 10
arrivalRate: 20
defaults:
headers:
from: 'header'
processor: "./shi_users_generator.js"
scenarios:
- name: "Authenticating a user"
flow:
# call getUser() to create the name, email, and password variables
- function: "getUser"
- post:
url: "/authentication"
json:
strategy: "local"
email: "{{ email }}"
password: "{{ password }}"
# Print the data we're sending while debugging the script:
- log: "Sent a request to /authentication with {{ email }}, {{ password }}"
there is a file called shi_users_generator.js in the same directory with the test and has a method called getUser
node.js socket.io load-testing cpu-usage feathersjs
add a comment |
When I make load test using Artillery to my feathers app that uses socketio as transport the CPU spikes to 100% and more. my production environment is digital ocean droplet with 2 CPU cores and 4GB of RAM. My test script is:
config:
target: "http://104.248.160.95:3030"
engine: 'socketio'
phases:
- duration: 10
arrivalRate: 20
defaults:
headers:
from: 'header'
processor: "./shi_users_generator.js"
scenarios:
- name: "Authenticating a user"
flow:
# call getUser() to create the name, email, and password variables
- function: "getUser"
- post:
url: "/authentication"
json:
strategy: "local"
email: "{{ email }}"
password: "{{ password }}"
# Print the data we're sending while debugging the script:
- log: "Sent a request to /authentication with {{ email }}, {{ password }}"
there is a file called shi_users_generator.js in the same directory with the test and has a method called getUser
node.js socket.io load-testing cpu-usage feathersjs
When I make load test using Artillery to my feathers app that uses socketio as transport the CPU spikes to 100% and more. my production environment is digital ocean droplet with 2 CPU cores and 4GB of RAM. My test script is:
config:
target: "http://104.248.160.95:3030"
engine: 'socketio'
phases:
- duration: 10
arrivalRate: 20
defaults:
headers:
from: 'header'
processor: "./shi_users_generator.js"
scenarios:
- name: "Authenticating a user"
flow:
# call getUser() to create the name, email, and password variables
- function: "getUser"
- post:
url: "/authentication"
json:
strategy: "local"
email: "{{ email }}"
password: "{{ password }}"
# Print the data we're sending while debugging the script:
- log: "Sent a request to /authentication with {{ email }}, {{ password }}"
there is a file called shi_users_generator.js in the same directory with the test and has a method called getUser
node.js socket.io load-testing cpu-usage feathersjs
node.js socket.io load-testing cpu-usage feathersjs
asked Nov 23 '18 at 5:47
user3642211
65
65
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53441221%2fcpu-spike-when-using-feathers-socketio%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53441221%2fcpu-spike-when-using-feathers-socketio%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown