Post by account_disabled on Feb 25, 2024 3:20:55 GMT
The So dont hesitate to leverage the power of database caching to unlock a smoother and more efficient user experience. At Prisma we aim to simplify the process of caching for developers. infrastructure can be tricky and timeconsuming so we built Accelerate as a solution that makes it easy to cache your database query results in a simple and predictable way. Follow us on Twitter or join us on Slack and Discord to learn more about the tools were building. Prisma 5 Faster by Default Alex Ruheni ruhenia lex Prisma 5 introduces changes that make it significantly faster. These changes especially improve the experience of using Prisma in serverless environments thanks to a new and more efficient JSONbased wire protocol that Prisma Client uses under the hood.
Prisma 5 Improved startup performance in Prisma Client From Prisma we have doubled down on our efforts to improve Prismas performance and Switzerland Mobile Number List developer experience. In particular we focused on improving Prismas startup performance in serverless environments. In our quest to improve Prismas performance we unearthed a few inefficiencies which we tackled. To illustrate the difference since we began investing our efforts in improving performance consider the following graphs below. The first graph represents the startup performance of an app deployed to AWS Lambda with a comparatively large Prisma schema.
Models before we began our efforts to improve it Before The following graph shows Prisma 5s performance after our work on performance improvements After As you can see there is a significant improvement in Prismas startup performance. Well now dig in and discuss the various changes that got us to this much improved state. A more efficient JSONbased wire protocol Prior to Prisma 4.11.0 Prisma used a GraphQLlike protocol to communicate between Prisma Client and the query engine. This came with a few quirks that impacted Prisma Clients performance especially on cold starts in serverless environments. During our performance exploration we noticed that the current implementation added a considerable CPU and memory.
Prisma 5 Improved startup performance in Prisma Client From Prisma we have doubled down on our efforts to improve Prismas performance and Switzerland Mobile Number List developer experience. In particular we focused on improving Prismas startup performance in serverless environments. In our quest to improve Prismas performance we unearthed a few inefficiencies which we tackled. To illustrate the difference since we began investing our efforts in improving performance consider the following graphs below. The first graph represents the startup performance of an app deployed to AWS Lambda with a comparatively large Prisma schema.
Models before we began our efforts to improve it Before The following graph shows Prisma 5s performance after our work on performance improvements After As you can see there is a significant improvement in Prismas startup performance. Well now dig in and discuss the various changes that got us to this much improved state. A more efficient JSONbased wire protocol Prior to Prisma 4.11.0 Prisma used a GraphQLlike protocol to communicate between Prisma Client and the query engine. This came with a few quirks that impacted Prisma Clients performance especially on cold starts in serverless environments. During our performance exploration we noticed that the current implementation added a considerable CPU and memory.