Please grow your buffers exponentially
blog.mozilla.org
Please grow your buffers exponentially
1–10 of 166 posts
Re: Please grow your buffers exponentially
#2Is there a reason the link is directed to a comment?
Re: Please grow your buffers exponentially
#3Is there a reason the link is directed to a comment?
Yes. I'm an idiot, and it's been more than 15 minutes since I posted it, so I can't trim the URL!
If there are any mods about, I'd appreciate their help...
Re: Please grow your buffers exponentially
#4From the comments, the linked SO question is probably better a treat of the title than the article:
http://stackoverflow.com/questions/1100311/what-is-the-ideal...
I would have guessed by now it is common knowledge that you should grow your buffers exponentially. The only question being by how much?
For general usage it seems 1.5 is usually used but another factor could be better if you have different constraints for reallocating and memory fragmentation or value them differently.
Re: Please grow your buffers exponentially
#5Not using exponential growth in buffers / vectors / other contiguously allocated collections is a rookie mistake. It shouldn't be made by anyone who's ever studied algorithm complexity, never mind studied CS at any level.
About the only exception is when you have global knowledge about how a buffer is going to be used. But that's rare in modern modular software.
Re: Please grow your buffers exponentially
#6Not using exponential growth in buffers / vectors / other contiguously allocated collections is a rookie mistake. It shouldn't be made by anyone who's ever studied algorithm complexity, never mind studied CS at any level. About the only exception is when you have global knowledge about how a buffer is going to be used. But that's rare in modern modular software.
Not even thinking about the buffers being used to actually store your data is more like it.
Re: Please grow your buffers exponentially
#7Not using exponential growth in buffers / vectors / other contiguously allocated collections is a rookie mistake. It shouldn't be made by anyone who's ever studied algorithm complexity, never mind studied CS at any level. About the only exception is when you have global knowledge about how a buffer is going to be used. But that's rare in modern modular software.
What a remarkably misguided rant.
To each his own. What works for a general-purpose app on a desktop hardware doesn't work for a resource-constrained firmware (that still has to deal with potentially unbounded inputs). Yes, there's exponential reallocation, but there's also a multitude of other strategies, each best fit for its particular application domain. "Rookie mistake".
Re: Please grow your buffers exponentially
#8Not using exponential growth in buffers / vectors / other contiguously allocated collections is a rookie mistake. It shouldn't be made by anyone who's ever studied algorithm complexity, never mind studied CS at any level. About the only exception is when you have global knowledge about how a buffer is going to be used. But that's rare in modern modular software.
[deleted]
Re: Please grow your buffers exponentially
#9Not using exponential growth in buffers / vectors / other contiguously allocated collections is a rookie mistake. It shouldn't be made by anyone who's ever studied algorithm complexity, never mind studied CS at any level. About the only exception is when you have global knowledge about how a buffer is going to be used. But that's rare in modern modular software.
What a remarkably misguided rant. To each his own. What works for a general-purpose app on a desktop hardware doesn't work for a resource-constrained firmware (that still has to deal with potentially unbounded inputs). Yes, there's exponential reallocation, but there's also a multitude of other strategies, each best fit for its particular application domain. "Rookie mistake".
[deleted]
Re: Please grow your buffers exponentially
#10https://areweslimyet.com/ seems badly named: all the curves are trending upwards, so it seems like it should be "wellneverbeslim.com"