Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve docs around AllocationLimitMegabytes #69

Open
antonfirsov opened this issue Dec 16, 2024 · 0 comments
Open

Improve docs around AllocationLimitMegabytes #69

antonfirsov opened this issue Dec 16, 2024 · 0 comments

Comments

@antonfirsov
Copy link
Member

Noting down a couple of improvement ideas after re-reading some docs I made.

- Imposing conservative allocation limits by configuring a custom MemoryAllocator
+ Imposing conservative allocation limits by configuring a custom MemoryAllocator with [`MemoryAllocationOptions.AllocationLimitMegabytes`](https://docs.sixlabors.com/api/ImageSharp/SixLabors.ImageSharp.Memory.MemoryAllocatorOptions.html#SixLabors_ImageSharp_Memory_MemoryAllocatorOptions_AllocationLimitMegabytes) set to a value lower value.
  • Link back the security docs from the property docs.
  • For both the MaximumPoolSizeMegabytes docs and AllocationLimitMegabytes can be more precise about defining the default value:
- null means platform default: 1GB on 32-bit processes, 4GB on 64-bit processes.
+ The value is null by default, which means platform defaults will be used: 1GB on 32-bit processes, 4GB on 64-bit processes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant