--- title: Amazon EMR Serverless now supports larger worker sizes... description: Amazon EMR Serverless now supports larger worker configurations of 32 vCPUs with up to 244 GB of memory, doubling the previous maximum of 16 vCPUs and 120 GB.... canonical: https://daily.dev/posts/amazon-emr-serverless-now-supports-larger-worker-sizes-to-run-more-compute-and-memory-intensive-work-ykeqytnir twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Amazon EMR Serverless now supports larger worker sizes to run more compute and memory intensive workloads | daily.dev og:description: Amazon EMR Serverless now supports larger worker configurations of 32 vCPUs with up to 244 GB of memory, doubling the previous maximum of 16 vCPUs and 120 GB.... og:url: https://daily.dev/posts/amazon-emr-serverless-now-supports-larger-worker-sizes-to-run-more-compute-and-memory-intensive-work-ykeqytnir og:image: https://api.daily.dev/og/posts/yKeQYTNir.png og:image:alt: Amazon EMR Serverless now supports larger worker sizes to run more compute and memory intensive workloads og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Amazon EMR Serverless now supports larger worker sizes to run more compute and memory intensive workloads **[AWS](https://daily.dev/sources/aws)** · 1 min read · 0 upvotes · 0 comments ## Summary Amazon EMR Serverless now supports larger worker configurations of 32 vCPUs with up to 244 GB of memory, doubling the previous maximum of 16 vCPUs and 120 GB. These larger workers benefit shuffle-heavy workloads by reducing data transfers between executors, help avoid out-of-memory failures for skewed data jobs, and allow more data to be cached in memory. The feature is available in all AWS regions where EMR Serverless is supported and is recommended for compute and memory-intensive Spark and Hive workloads. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [AWS Lambda supports up to 32 GB of memory and 16 vCPUs for Lambda Managed Instances](https://daily.dev/posts/aws-lambda-supports-up-to-32-gb-of-memory-and-16-vcpus-for-lambda-managed-instances-jp3xptauv) · AWS · 0 upvotes · 0 comments - [Amazon EMR Serverless now supports Apache Spark 4.0.1 \(preview\)](https://daily.dev/posts/amazon-emr-serverless-now-supports-apache-spark-4-0-1-preview--mckowuiut) · AWS · 0 upvotes · 0 comments - [Amazon EMR Serverless now supports live configuration updates without application restarts](https://daily.dev/posts/amazon-emr-serverless-now-supports-live-configuration-updates-without-application-restarts-byrmllvf2) · AWS · 0 upvotes · 0 comments --- Tags: [#aws](https://daily.dev/tags/aws), [#serverless](https://daily.dev/tags/serverless), [#big-data](https://daily.dev/tags/big-data), [#apache-spark](https://daily.dev/tags/apache-spark) [View this post on daily.dev](https://daily.dev/posts/amazon-emr-serverless-now-supports-larger-worker-sizes-to-run-more-compute-and-memory-intensive-work-ykeqytnir) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Amazon EMR Serverless now supports larger worker sizes to run more compute and memory intensive workloads","url":"https://daily.dev/posts/amazon-emr-serverless-now-supports-larger-worker-sizes-to-run-more-compute-and-memory-intensive-work-ykeqytnir","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/amazon-emr-serverless-now-supports-larger-worker-sizes-to-run-more-compute-and-memory-intensive-work-ykeqytnir"},"datePublished":"2026-07-07T20:06:13.297Z","dateModified":"2026-08-24T06:50:14.752Z","description":"Amazon EMR Serverless now supports larger worker configurations of 32 vCPUs with up to 244 GB of memory, doubling the previous maximum of 16 vCPUs and 120 GB....","image":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","thumbnailUrl":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","isAccessibleForFree":true,"articleSection":"AWS","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"AWS","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/aws","url":"https://daily.dev/sources/aws"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/amazon-emr-serverless-now-supports-larger-worker-sizes-to-run-more-compute-and-memory-intensive-work-ykeqytnir","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"aws,serverless,big-data,apache-spark","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"AWS","item":"https://daily.dev/sources/aws"},{"@type":"ListItem","position":3,"name":"Amazon EMR Serverless now supports larger worker sizes to run more compute and memory intensive workloads"}]} ```