Blockscout Simple Load testing

[diminator]

• load test GraphQL API with >= 50 connections
• test complex GraphQL queries that could brake the instance
• load test the web frontend

[aaitor]

After some analysis of the integration of Absinthe into Blockscout, some details:

• Blockscout includes an initial integration of max_complexity filter of Absinthe
  https://hexdocs.pm/absinthe/complexity-analysis.html

• It uses a max_complexity of 200 that can be found in lib/block_scout_web/router.ex

• The filter by complexity needs to be integrated in each Graphql query, currently is only included in:

  • Gets addresses by address hash.
  • Gets token transfers by token contract address hash

My suggestion on that would be:

• Identify potential Graphql queries to protect
• Implement & test the max_complexity filter in each of those
• Evaluate if we need different thresholds per query or the general threshold of 200 is good enough

[aaitor]

Blockscout PR: celo-org/blockscout#93

[aaitor]

Graphql api test scenario:

• Running in a server with 8GB RAM and 1vCPU
• Using alfajores data
• 50 virtual users * 22 minutes

All virtual users finished
Summary report @ 14:24:00(+0200) 2020-04-07
  Scenarios launched:  500
  Scenarios completed: 500
  Requests completed:  111500
  Mean response/sec: 82.3
  Response time (msec):
    min: 51.9
    max: 45484.1
    median: 3452.7
    p95: 19940.1
    p99: 32707.5
  Scenario counts:
    GraphQL Query load test: 500 (100%)
  Codes:
    200: 111500

Done in 1356.75s.

Running that scenario we didn't find any error code

[aaitor]

Load tested the UI using JMeter with 25 concurrent users. No errors found.