Allocating memory on the heap can slow a program down by creating work for the .NET garbage collector. In C# we can improve performance by using the stack instead.
Source code available at: github.com/JasperKent/Spans-a...
Topics include:
- Referencing contiguous memory with Span and ReadOnlySpan
- Allocating on the stack with stackalloc
- Writing high performance methods with zero heap allocation
- Avoiding the need for unsafe code
- Fast text parsing
Do you have performance problems because of heap allocation? Let me know in the comments. Source code available at: github.com/JasperKent/Spans-and-stackalloc Remember to subscribe at kzhead.info/tools/qWQzlUDdllnLmtgfSgYTCA.html And if you liked the video, click the 👍.
My viewpoint is that heap alloc is pure evil and should only be done as a setup step and almost never as part of routine runtime unless storing data. But I'm a graphics/rendering programmer so that means my environment is rather radically different from the norm!
I haven't seen anyone explaining Spans this simple and clear way, thank you Sir.
Amazing video as always! A small correction, at 8:24, you say that a list may not be a contiguous space in memory, actually the list will always be a contiguous space in memory because it is just a wrapper over the c# array, the reason is that when the list grows bigger than its initial length , it will create a new array and copy the old one, but the span will still point to the space in memory where the previous array was . That's why we have the CollectionsMarshal.AsSpan(List) Method, but is only safe to use when we are sure that the list won't relocate the array.
Absolutely right.
This is what is called "Perfection and Dedication". Thank you sir.
Your videos are awesome. I wish everybody would watch them and update their C# knowledge to modern practices. Unfortunately many people are happy to bump .NET to 7 and C# to preview but didn't bump their coding so I still see recent C# that looks very old. Also, in your fast parser you could very easily determine the starts/ends of each number and pass just that section of the Span to the double parser. That should definitely yield more time improvements without all that copying. Keep up the awesome work!
Yeah, there's more room for optimization, but getting things off the heap is the big one.
So happy I found your channel! Great video. I plan on subscribing and going through your backlog as this is a great explanation of Span
I love your content! It's so clearly explained. Thank you sir
A very good example to show to a junior when explaining how evil early optimazation can be. Just as the speaker said, only do this when you really-really have to. 😊
Absolutely. I've never needed to do this is real life.
Thanks sir, your explanations are crystal clear. Absolutely loving the video
Another great edition of Coding Tutorials.!
Sir, this tutorial is amazing, just like your costume!)
Once again a perfectly explained video :) Thank you!
THANK You Sir
How can we return a Span from a function? Or any value type that has more than one field in it? In my understanding, when we return from a function, we pop the activation record, then pop the return address and follow it back to the caller. Since this pops the span from the stack, how do we use it in the calling function? With heap allocation, we can store a pointer in a register and use that to refer to the memory. Yet if we store a stack pointer to now unallocated memory, that wouldn't be good. So I'm really confused on how this would be used if returned from a function.
Thanks!
Are you sure that you need 'number.Fill' at all? After the stackalloc, 'number' should contain only #0 chars, if you don't have a SkipLocalsInit attribute. You could pass a slice of 'number' between zero and 'pos' to double.Parse.
i couldn't understand the benefit of Span if i am able to modify in copy array and changes are reflected in original array too then whats the use i want my copied array changes shouldn't be modified in original array.
The benefit is that you save the performance overhead of doing a copy. The modification is a side-effect that you may or may not want. If you don't want it, you can either use a ReadonlySpan and prevent changes at all, or take the performance hit of doing a copy.
Do you use also Blazor ?
Sometimes, though it's not as widely used as things like Angular or React.