Skip to content

Instantly share code, notes, and snippets.

@ankitadhandha
Last active December 24, 2020 13:03
Show Gist options
  • Save ankitadhandha/17c33c63e803a01612088b1a5b87ce64 to your computer and use it in GitHub Desktop.
Save ankitadhandha/17c33c63e803a01612088b1a5b87ce64 to your computer and use it in GitHub Desktop.

AWS/Lambda limits

  1. Application size/footprint
  • 250MB
  1. Application duration/runtime
  • 29 seconds
  • note: AWS/Lambda uses API Gateway
  1. Available AWS/Lambda memory
  • 2.5GB

Our steps to configure SDL for AWS/Lambda

Application size/footprint

  1. Process
  • Reduced standard SDL footprint from greater than 300MB to less than 250MB
  1. Implications
  • Limits ability to analyze structured data using ontologies in addition to schema.org
    • See plans for Release 0.3, 0.4 and 0.5

Application duration/runtime

  1. Process
  • Experiment with document size
  • Experiment with structured data complexity (third normal form)
  1. Implications
  • File size limit (third normal form): 490KB
  • File size limit (first normal form): less than 490KB
  1. Comparison
  • Google SDTT file size limit is 2.5MB

Potential methods to use AWS/Lambda more efficiently

  1. AWS/Lambda memory
  • May be able to malloc up to 10GB
  1. Application size/footprint
  • Remove more non-essential SDL features
  1. Application duration/runtime
  • Implement concurrent/multi-threaded workload
    • Preliminary experiments with asynchronous processing on AWS/Lambda failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment