In .NET enumeration is slow
-
Quote:
I actually did dotNetPeek them
In my experience, I have found peeking and looking at the actual source code is not always the same thing. The compiler tends to optimise and rewrite code these days...
Graeme
"I fear not the man who has practiced ten thousand kicks one time, but I fear the man that has practiced one kick ten thousand times!" - Bruce Lee
In that case I wasn't as interested in the source code as I was in the final code. I was looking for optimization opportunities, and I was looking at the IL as well and comparing it to mine.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
It's not 20ms. it's a 30% improvement in overall execution time. If I increase the test size to run for 90 seconds, it would run for about 60 after the optimization. If you get even 20% off the execution in critical code paths it's generally worth the optimization. I mean, of course it depends on the circumstances, and is less true of business development, or development with large teams or teams with with a lot of turnover, where you can't afford the additional maintenance overhead, limited knowledge transferability and cognitive load of optimized code. That is not a microoptimization. 30% off total execution time is a significant savings. Adding, I used to use garbage collection in my ISAPI applications because it prevented nasty heap fragmentation due to all the string processing required of web servers. It made things faster. GC isn't always a losing performance proposition. When the situation calls for it, it can increase overall performance.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
30% in overall execution time? Does your code consist mostly of enumerations and while loops? No, it doesn't go from 90 to 60, unless all your code is enumerate. Real world code is more than just retrieving a list. Sorry Honey. VS shows you the place where it spends most time. "Limited knowledge trans...", aight, you're allowed to your views, I have mine. And yes, mucking about a for loop vs enumerable in an VB6 runtime (which .NET IS) is not even a microoptimization, it is purely whining. Write in a goddamn real language if it is that important an link to it from .NET where you need it. You have fallen, my angel, and very deep. Time critical stuff isn't worth .NET, and it isn't worth my time to read about 20 ms savings in a different loop that is less readable. When the situation calls for it, you want someone who works with pointers, not with .NET. I would write a library for you to link to that does the heavy lifting, "if the situation calls for it". Because .NET is just an evolution of VB6, it is just a runtime interpreting with a memory manager. It is vbruntime600 with additional libraries. Any compiled language with pointers laughs out loud. This is not even an argument honey. EVERYONE can use a profiler and see how much your micro optimization may help them. If it does, then yay for them for writing ineffcient code. My code does not consist of merely enumerations, it deals with a lot more stuff. Real world code consist of more than "looping". And if speed is that paramount then why are you using .NET? Are you really blabbing about how to do a for loop in a VB-variant? That is what C# is, VB6 in a new interface, but that translates 1 on 1 to VB. You really whining about the performance of BASIC code (by any other syntax, but still a rose/VB)? And you prove it by throwing some unreadable code, that saves me 20 ms? That is going to impress, really. You will shave of some ms, sacrificing readability for some code that takes more than 2 secs? Did you know that humans only see 48 frames per second? The END USER will not even notice, but the manager that pays someone to update your code WILL. You're gonna go far kid.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
Welcome to my bandwagon. I've been saying this for ages. Don't use
foreachunless you have to -- or where it doesn't matter. Having said that... I hypothesize thatforeachhas improved. To test this hypothesis, last summer (?) I was testing and measuring some comparisons and I didn't see much difference. I was unable to form conclusions at that time because I wasn't convinced that the tests were valid. I'll have another look later. P.S. And besides, you mean iteration, not enumeration -- I blame Microsoft for misnaming the thing.You "think"? We do not think, we measure. If you say that you think, you think that you think. Measure or shut the elephant op.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
Of course it's slower. The IEnumerable interface expects a class with methods you have to call to maintain which item in the IEnumerable implementor you're looking at. Calling methods adds overhead, and plenty of it compared to the overhead of an index variable, which you know is just pointer math. Enumerable being slower is not surprising at all. Just don't use it where you don't have to, and that includes LINQ because it's heavily dependent on the IEnumerable interfaces.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak
Upvoted and sorry. It is a decision. Do you want the best in speed? Or do you just need to get things done and be readable?
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
30% in overall execution time? Does your code consist mostly of enumerations and while loops? No, it doesn't go from 90 to 60, unless all your code is enumerate. Real world code is more than just retrieving a list. Sorry Honey. VS shows you the place where it spends most time. "Limited knowledge trans...", aight, you're allowed to your views, I have mine. And yes, mucking about a for loop vs enumerable in an VB6 runtime (which .NET IS) is not even a microoptimization, it is purely whining. Write in a goddamn real language if it is that important an link to it from .NET where you need it. You have fallen, my angel, and very deep. Time critical stuff isn't worth .NET, and it isn't worth my time to read about 20 ms savings in a different loop that is less readable. When the situation calls for it, you want someone who works with pointers, not with .NET. I would write a library for you to link to that does the heavy lifting, "if the situation calls for it". Because .NET is just an evolution of VB6, it is just a runtime interpreting with a memory manager. It is vbruntime600 with additional libraries. Any compiled language with pointers laughs out loud. This is not even an argument honey. EVERYONE can use a profiler and see how much your micro optimization may help them. If it does, then yay for them for writing ineffcient code. My code does not consist of merely enumerations, it deals with a lot more stuff. Real world code consist of more than "looping". And if speed is that paramount then why are you using .NET? Are you really blabbing about how to do a for loop in a VB-variant? That is what C# is, VB6 in a new interface, but that translates 1 on 1 to VB. You really whining about the performance of BASIC code (by any other syntax, but still a rose/VB)? And you prove it by throwing some unreadable code, that saves me 20 ms? That is going to impress, really. You will shave of some ms, sacrificing readability for some code that takes more than 2 secs? Did you know that humans only see 48 frames per second? The END USER will not even notice, but the manager that pays someone to update your code WILL. You're gonna go far kid.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
> 30% in overall execution time? Does your code consist mostly of enumerations and while loops? In this case yes, in fact I posted the code, which is a regex matching algorithm. > And yes, mucking about a for loop vs enumerable in an VB6 runtime (which .NET IS) is not even a microoptimization, it is purely whining. Write in a goddamn real language if it is that important an link to it from .NET where you need it. I wasn't whining. I was making an observation. You're looking for a fight. I have better things to do with my time. Grow up. Also VB.NET and VB6 runtimes have nothing to do with each other. You don't even know what you're talking about. Funny how arrogance and ignorance go hand in hand so often.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
It's not 20ms. it's a 30% improvement in overall execution time. If I increase the test size to run for 90 seconds, it would run for about 60 after the optimization. If you get even 20% off the execution in critical code paths it's generally worth the optimization. I mean, of course it depends on the circumstances, and is less true of business development, or development with large teams or teams with with a lot of turnover, where you can't afford the additional maintenance overhead, limited knowledge transferability and cognitive load of optimized code. That is not a microoptimization. 30% off total execution time is a significant savings. Adding, I used to use garbage collection in my ISAPI applications because it prevented nasty heap fragmentation due to all the string processing required of web servers. It made things faster. GC isn't always a losing performance proposition. When the situation calls for it, it can increase overall performance.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Any other day, this would go. Today is not that day. It isn't 30% even if all you do is enumerate. GC's is losing performance by definition of what the beast is made of. Show me one example of .NET that outperforms Delphi? Where, o where, would an interpreter with a lot of libraries outperform a compiled native language? You .NET dev? Than you write in VB7, complete with a GC and a runtime interpreter. Your code will be faster than anything I write in a real compiler, innit? And your 20 ms on 60 is gonna make a 30% if it is only enumerating, because all that code does is enumerate. I am not even amused a bit. Obfuscation to save a few ms. Yeah, that will help, really. You saved the world, but the rest of us are going to use enumerations because it is a damned good tradeof for those that only know .NET and cannot handle pointers. It makes code readable, which yours damned ain't. Great, you reduced some code by 20 ms. Most code takes longer. Was there anything else you'd like to whine about, or are we done? :| BPFH :suss:
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
> 30% in overall execution time? Does your code consist mostly of enumerations and while loops? In this case yes, in fact I posted the code, which is a regex matching algorithm. > And yes, mucking about a for loop vs enumerable in an VB6 runtime (which .NET IS) is not even a microoptimization, it is purely whining. Write in a goddamn real language if it is that important an link to it from .NET where you need it. I wasn't whining. I was making an observation. You're looking for a fight. I have better things to do with my time. Grow up. Also VB.NET and VB6 runtimes have nothing to do with each other. You don't even know what you're talking about. Funny how arrogance and ignorance go hand in hand so often.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
A fringe case, as most of us do not write regex-libs, and anyone who would doesn't use an interpreter but a compiler. No, not a byte code compiler, that's just a fancy marketing shit for an interpreter that doesn't compile to native. And yes, I'm looking for a fight; you are implying that some loop in an interpreter is interesting. It isn't. VB.NET and VB6 are ridiculously the same. I've done that discussion a thousand times, where a manager imagined C# to be superior to VB.NET. It is a different syntax for the same VBRUN300.DLL, a fakkin interpreter that does bytecode like VB6 did with the same memory manager. C# is marketing, but under the hood it is just VB7 with a different style of writing. Which is brilliant from an MS perspective btw, which proves MS is still the best. Now, get off my lawn.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
A fringe case, as most of us do not write regex-libs, and anyone who would doesn't use an interpreter but a compiler. No, not a byte code compiler, that's just a fancy marketing shit for an interpreter that doesn't compile to native. And yes, I'm looking for a fight; you are implying that some loop in an interpreter is interesting. It isn't. VB.NET and VB6 are ridiculously the same. I've done that discussion a thousand times, where a manager imagined C# to be superior to VB.NET. It is a different syntax for the same VBRUN300.DLL, a fakkin interpreter that does bytecode like VB6 did with the same memory manager. C# is marketing, but under the hood it is just VB7 with a different style of writing. Which is brilliant from an MS perspective btw, which proves MS is still the best. Now, get off my lawn.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Linq makes it not a fringe case since it uses enumerations all over the place. It's also a known documented issue with .NET. I'm far from the first person to make this observation. Folks from Microsoft have said as much. And yes, you're looking for a fight. I'm an adult, which is why I was looking for a discussion. You're clearly not capable of something like that so we're done. Feel free to keep running your mouth about .NET, in case anyone wasn't already convinced that you don't know half of what you're on about.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
Linq makes it not a fringe case since it uses enumerations all over the place. It's also a known documented issue with .NET. I'm far from the first person to make this observation. Folks from Microsoft have said as much. And yes, you're looking for a fight. I'm an adult, which is why I was looking for a discussion. You're clearly not capable of something like that so we're done. Feel free to keep running your mouth about .NET, in case anyone wasn't already convinced that you don't know half of what you're on about.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Quote:
Linq makes it not a fringe case since it uses enumerations all over the place.
You disliked Linq? Normal code doesn't require Linq? Did you make this microoptimization to prove you're better than Linq?
Quote:
It's also a known documented issue with .NET. I'm far from the first person to make this observation. Folks from Microsoft have said as much.
Is that the basis of your post? Maybe you missed the point; 20 ms is nothing in a background thread, and I would remove your code from any codebase for being unreadable and obfuscating. I gladly pay a few ms for readability, maintenance and fewer bugs. That is implying that there's only .NET devs and that there's no person available who can write in a language that compiles to native. You call those things "libraries".
Quote:
And yes, you're looking for a fight. I'm an adult, which is why I was looking for a discussion. You're clearly not capable of something like that so we're done.
So, that is your defense? You little twat copied MS and you can't handle me saying it ain't so? Thank you for the limitless list of arguments and examples. Wait, there's none? "Folks from MS have said".. and you copied and try to impress. Sorry, but you didn't with your 20 ms. As if all code is a regex-lookup, which you present as if your micro optimization invalidates every foreach. If you want to regex, use a native language. I will
BREAKyour nonsense. I do not care about you copying MS and presenting it as "your" observation. I just puke over the generalization :suss:Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
Quote:
Linq makes it not a fringe case since it uses enumerations all over the place.
You disliked Linq? Normal code doesn't require Linq? Did you make this microoptimization to prove you're better than Linq?
Quote:
It's also a known documented issue with .NET. I'm far from the first person to make this observation. Folks from Microsoft have said as much.
Is that the basis of your post? Maybe you missed the point; 20 ms is nothing in a background thread, and I would remove your code from any codebase for being unreadable and obfuscating. I gladly pay a few ms for readability, maintenance and fewer bugs. That is implying that there's only .NET devs and that there's no person available who can write in a language that compiles to native. You call those things "libraries".
Quote:
And yes, you're looking for a fight. I'm an adult, which is why I was looking for a discussion. You're clearly not capable of something like that so we're done.
So, that is your defense? You little twat copied MS and you can't handle me saying it ain't so? Thank you for the limitless list of arguments and examples. Wait, there's none? "Folks from MS have said".. and you copied and try to impress. Sorry, but you didn't with your 20 ms. As if all code is a regex-lookup, which you present as if your micro optimization invalidates every foreach. If you want to regex, use a native language. I will
BREAKyour nonsense. I do not care about you copying MS and presenting it as "your" observation. I just puke over the generalization :suss:Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
*sigh* You're a child. And you can't even code in C or C++. Stop wagging your tiny little peen around like it's something. :laugh:
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
Quote:
Linq makes it not a fringe case since it uses enumerations all over the place.
You disliked Linq? Normal code doesn't require Linq? Did you make this microoptimization to prove you're better than Linq?
Quote:
It's also a known documented issue with .NET. I'm far from the first person to make this observation. Folks from Microsoft have said as much.
Is that the basis of your post? Maybe you missed the point; 20 ms is nothing in a background thread, and I would remove your code from any codebase for being unreadable and obfuscating. I gladly pay a few ms for readability, maintenance and fewer bugs. That is implying that there's only .NET devs and that there's no person available who can write in a language that compiles to native. You call those things "libraries".
Quote:
And yes, you're looking for a fight. I'm an adult, which is why I was looking for a discussion. You're clearly not capable of something like that so we're done.
So, that is your defense? You little twat copied MS and you can't handle me saying it ain't so? Thank you for the limitless list of arguments and examples. Wait, there's none? "Folks from MS have said".. and you copied and try to impress. Sorry, but you didn't with your 20 ms. As if all code is a regex-lookup, which you present as if your micro optimization invalidates every foreach. If you want to regex, use a native language. I will
BREAKyour nonsense. I do not care about you copying MS and presenting it as "your" observation. I just puke over the generalization :suss:Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
You seriously called me a "twat"? What the hell is wrong with you? You are a child. You can't even code in C or C++, and you talk about Delphi like that's a flex. It's a joke. You're a joke, and you're a belligerent clown. I've reported your account because this isn't the first time you've been abusive and hostile to other people.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
You seriously called me a "twat"? What the hell is wrong with you? You are a child. You can't even code in C or C++, and you talk about Delphi like that's a flex. It's a joke. You're a joke, and you're a belligerent clown. I've reported your account because this isn't the first time you've been abusive and hostile to other people.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Quote:
I've reported your account because this isn't the first time you've been abusive and hostile to other people.
I cannot argue that, as it is true. I do not have much patience.
Quote:
You are a child
You meant "childish". :suss:
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
Quote:
I've reported your account because this isn't the first time you've been abusive and hostile to other people.
I cannot argue that, as it is true. I do not have much patience.
Quote:
You are a child
You meant "childish". :suss:
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
I would have been happy to debate this with you. That changed when it became clear to me that weren't interested in actually debating anyone. You came here for a fight. You came here because you wanted to abuse other people. You have some issues, and you are making them the problem of other people here. That's not cool.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
> 30% in overall execution time? Does your code consist mostly of enumerations and while loops? In this case yes, in fact I posted the code, which is a regex matching algorithm. > And yes, mucking about a for loop vs enumerable in an VB6 runtime (which .NET IS) is not even a microoptimization, it is purely whining. Write in a goddamn real language if it is that important an link to it from .NET where you need it. I wasn't whining. I was making an observation. You're looking for a fight. I have better things to do with my time. Grow up. Also VB.NET and VB6 runtimes have nothing to do with each other. You don't even know what you're talking about. Funny how arrogance and ignorance go hand in hand so often.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Regex, now there's your real problem. :laugh: [xkcd: Perl Problems](https://xkcd.com/1171/)
-
I just switched IEnumerable to IList and removed foreach (preferring for) and cut my execution time in my test from 65ms to about 45ms. I've put a stripped down version of the code here. The first argument of each emphasized routine was IEnumerable, is now IList with no foreach. This, ladies and gents, is why I don't like LINQ.
// here this._fa is the target machine we will be parsing.
// parse this or otherwise build it and use it here.
IList initial = FA.FillEpsilonClosure(this._fa);
IList next = new List();
IList states = new List(initial);
// start out with an empty capture buffer
this.capture.Clear();
// first move:
if (this.current == -2)
{
this.Advance();
}
// store the current position
long cursor_pos = this.position;
int line = this.line;
int column = this.column;
while(true) {
// try to transition from states on
// the current codepoint under the
// cursor
next.Clear();
FA.FillMove(states, this.current, next);
if (next.Count > 0)
{
// found at least one transition
// capture the current
// char, advance the input
// position:
this.Advance();
// move to the next states
states.Clear();
FA.FillEpsilonClosure(next, states);
} else {
// no matching transition
// is any current state accepting?
int acc = FA.GetFirstAcceptSymbol(states);
if(acc>-1) {
// accept
return FAMatch.Create(
acc,
this.capture.ToString(),
cursor_pos,
line,
column);
}
// not accepting - error
// keep capturing input until we find a
// valid move or there's no more input
while (this.current != -1 &&
FA.FillMove(initial, this.current).Count == 0)
{
this.Advance();
}
if (capture.Length == 0)
{
// end of input
return FAMatch.Create(-2, null, 0, 0, 0);
}
// error
return FAMatch.Create(-1,
capture.ToString(),
cursor_pos,
line,
column);}}
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Having written .Net enumerators, yes, it can be slow. It can also be a very powerful abstraction when used properly. Linq on the other hand, is a nightmare to write in VB. C# supports the Lambda syntax while VB doesn't. Personally, most Linq uses can easily be rewritten as a for loop which is easier to read and understand. Some require a function call, but then so do all Linq statements.
-
Quote:
I've reported your account because this isn't the first time you've been abusive and hostile to other people.
I cannot argue that, as it is true. I do not have much patience.
Quote:
You are a child
You meant "childish". :suss:
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Not taking sides, but your posts are so much like the arguments I used to hear from my fellow Navy nucs. I kind of miss it, but we Navy nucs re an odd lot. :)
-
A fringe case, as most of us do not write regex-libs, and anyone who would doesn't use an interpreter but a compiler. No, not a byte code compiler, that's just a fancy marketing shit for an interpreter that doesn't compile to native. And yes, I'm looking for a fight; you are implying that some loop in an interpreter is interesting. It isn't. VB.NET and VB6 are ridiculously the same. I've done that discussion a thousand times, where a manager imagined C# to be superior to VB.NET. It is a different syntax for the same VBRUN300.DLL, a fakkin interpreter that does bytecode like VB6 did with the same memory manager. C# is marketing, but under the hood it is just VB7 with a different style of writing. Which is brilliant from an MS perspective btw, which proves MS is still the best. Now, get off my lawn.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
"and anyone who would doesn't use an interpreter but a compiler. No, not a byte code compiler, that's just a fancy marketing sh*t for an interpreter that doesn't compile to native." Far as my limited experience goes C#, Java and JavaScript use an interpreter for their regexes. And I know Perl does. I suspect JavaScript like Perl cannot be anything but an interpreter (in most usages.) At least for Java it might at some point go Native. Same could be true of C#.
-
Regex, now there's your real problem. :laugh: [xkcd: Perl Problems](https://xkcd.com/1171/)
-
I just switched IEnumerable to IList and removed foreach (preferring for) and cut my execution time in my test from 65ms to about 45ms. I've put a stripped down version of the code here. The first argument of each emphasized routine was IEnumerable, is now IList with no foreach. This, ladies and gents, is why I don't like LINQ.
// here this._fa is the target machine we will be parsing.
// parse this or otherwise build it and use it here.
IList initial = FA.FillEpsilonClosure(this._fa);
IList next = new List();
IList states = new List(initial);
// start out with an empty capture buffer
this.capture.Clear();
// first move:
if (this.current == -2)
{
this.Advance();
}
// store the current position
long cursor_pos = this.position;
int line = this.line;
int column = this.column;
while(true) {
// try to transition from states on
// the current codepoint under the
// cursor
next.Clear();
FA.FillMove(states, this.current, next);
if (next.Count > 0)
{
// found at least one transition
// capture the current
// char, advance the input
// position:
this.Advance();
// move to the next states
states.Clear();
FA.FillEpsilonClosure(next, states);
} else {
// no matching transition
// is any current state accepting?
int acc = FA.GetFirstAcceptSymbol(states);
if(acc>-1) {
// accept
return FAMatch.Create(
acc,
this.capture.ToString(),
cursor_pos,
line,
column);
}
// not accepting - error
// keep capturing input until we find a
// valid move or there's no more input
while (this.current != -1 &&
FA.FillMove(initial, this.current).Count == 0)
{
this.Advance();
}
if (capture.Length == 0)
{
// end of input
return FAMatch.Create(-2, null, 0, 0, 0);
}
// error
return FAMatch.Create(-1,
capture.ToString(),
cursor_pos,
line,
column);}}
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Yeah, and it's not like there aren't developers that that have sweated over how to make that particular segment of code as fast as they can. There is a crap ton of flexibility built into IEnumerable that would be difficult to optimize away. I worked on a project years back where that level of optimization made a big difference, and I still used the convenience of LINQ group by, distinct, orderby, etc. to build up hashtables that I used in the optimized sections of code I wrote. Using LINQ helped in the part it was good at.
Curvature of the Mind now with 3D
-
It's not 20ms. it's a 30% improvement in overall execution time. If I increase the test size to run for 90 seconds, it would run for about 60 after the optimization. If you get even 20% off the execution in critical code paths it's generally worth the optimization. I mean, of course it depends on the circumstances, and is less true of business development, or development with large teams or teams with with a lot of turnover, where you can't afford the additional maintenance overhead, limited knowledge transferability and cognitive load of optimized code. That is not a microoptimization. 30% off total execution time is a significant savings. Adding, I used to use garbage collection in my ISAPI applications because it prevented nasty heap fragmentation due to all the string processing required of web servers. It made things faster. GC isn't always a losing performance proposition. When the situation calls for it, it can increase overall performance.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
