Stress test of subscriptions / methods

danielmain · August 22, 2019, 8:49am

Hello we used for a while meteor-down for simulating stress tests on the subscriptions and publications.

Together with APM it was a perfect combination to test our system.

Unfortunately since we updated to meteor 1.8.1 meteor-down is no more working.

Is there any good alternative to make the stress test for the methods and the subscriptions, simulationg many users?

Thanks!

tcastelli · August 22, 2019, 4:49pm

Would be interesting to discover a proper successor or a work-around

jkuester · August 23, 2019, 6:48am

Why not fork it and maintain it to run with the current and future releases? If it is has been a crucial feature in your setup it should be valuable for you to invest some time into doing that.

You can also utilize this post to draw some attention to the package and get some people to support your work

eluck · August 23, 2019, 1:58pm

Hey @danielmain,

We’ve built a load testing tool with first class Meteor and GraphQL support: https://astraload.com/astraload-saas/.

It can accurately reproduce user behavior and impose load to every single endpoint your application exposes, including Meteor methods and subscriptions, GraphQL resolvers and subscriptions, REST methods add raw websocket.

Please leave your contact data in a private message so we could proceed with stress testing your webapp.

sabativi · June 8, 2023, 10:19pm

Hey @eluck are you still running this ? Looking for tools to do stress tests

eluck · June 9, 2023, 4:31pm

Hey @sabativi, yes we’re still in business. Let’s do it!

paulishca · June 10, 2023, 5:26pm

github.com

meteorhacks/meteor-down-backdoor/blob/2313c967bfb389e0ef919d278f16ca5a07b550fa/lib/meteor-down.js#L24


      
          
          
    var user = Meteor.users.findOne(params.userId);
              if(!user) {
                throw new Meteor.Error(403, 'Incorrect userId', params);
              }
          
          
    // this is same as .setUserId(), but this does not add overhead
              // this does not resume subscriptions and so on, and we don't really need it
              // we do this at the start, so this is fine
              var sessionId = this.connection.id;
              var session = Meteor.server.sessions[sessionId];
              session.userId = user._id;
          
          
    return user;
            }
          });
          
          
MeteorDown = {};
          
          
MeteorDown.init = function (key) {
            this.key = key;

replace that line with

const session = Meteor.server.sessions.get(sessionId)

And for the NPM package, you can update dependencies and stop depending on coffee-script and replace with coffeescript. Ok just replace the packages.json with this:

{
  "name": "meteor-down",
  "version": "2.6.1",
  "description": "Load testing for Meteor",
  "repository": {
    "type": "git",
    "url": "https://github.com/meteorhacks/meteor-down.git"
  },
  "main": "./lib/mdown.js",
  "scripts": {
    "test": "./node_modules/mocha/bin/mocha"
  },
  "bin": {
    "meteor-down": "./bin/meteor-down.js"
  },
  "author": "Meteorhacks",
  "license": "MIT",
  "devDependencies": {
    "mocha": "^10.2.0"
  },
  "dependencies": {
    "coffeescript": "2.7.0",
    "ddp": "^0.12.1",
    "underscore": "1.13.6"
  }
}

Then in /bin/meteor-down.js replace in line 12
var coffee = require( "coffeescript" )
You can delete line 5 (require('http').globalAgent.maxSockets = 999999;). It is useless

You can install this NPM from a terminal or cmd while inside the NPM folder:

npm i -g @activitree/meteor-down@./

Everything else should be ok. Perhaps I will publish new variants under some new names
Cheers