Skip To Main Content
return provider.Create on Muck Rack

return provider.Create

As seen in: cnblogs.com
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work. Claim your profile
Back to return provider.Create’s profile

Articles by return provider.Create

【C#/.NET】使用ASP.NET Core对象池

|
By return provider.Create
| cnblogs.com
Nuget Microsoft.Extensions.ObjectPool 使用对象池的好处 减少初始化/资源分配，提高性能。这一条与线程池同理，有些对象的初始化或资源分配耗时长，复用这些对象减少初始化和资源分配。比如:我有一个执行耗时约500毫秒，内存空间 2KB的任务为此创建一个新线程异步执行，而创建线程耗时1秒，内存空间占用1MB则得不偿失。 使用步骤 安装Nuget包:Install-Package Microsoft.Extensions.ObjectPool builder.Services.TryAddSingleton<ObjectPoolProvider, DefaultObjectPoolProvider>(); 使用对象池的第一步是实现IPooledObjectPolicy接口，要告诉对象池如何创建需要复用的对象 IPooledObjectPolicy接口有两个方法， T Create()负责创建复用对象。 Return负责将复用的对象释放回对象池中。如果不调用Return，表示该对象在对象池被移除。 //对象池框架接口 public interface...
Open in Who Shared Issue with article?

Object reuse with ObjectPool in ASP.NET Core

|
By Steve Gordon, Ryan Nowak, return provider.Create, await context.Response.Write Async
| microsoft.com
Read in English Read in English Feedback Edit Twitter LinkedIn Facebook Email Article 09/07/2022 3 minutes to read In this article By Steve Gordon, Ryan Nowak, and G√ľnther Foidl Microsoft.Extensions.ObjectPool is part of the ASP.NET Core infrastructure that supports keeping a group of objects in memory for reuse rather than allowing the objects to be garbage collected. You might want to use the object pool if the objects that are being managed are: Expensive to allocate/initialize.
Open in Who Shared Issue with article?
Show More