I just noticed that the C++ packages "imath" and "openexr" can both
be built with an option called "large-stack."

Presumably, large-stack allows objects to be allocated on the
stack rather than the heap and this is much, much, much faster.

Thus, on Gentoo, I just added the "large-stack" option and the
two above packages were automagically re-built to use the stack.

I pity those poor distro lackeys that must accept their generic
junk.

My Gentoo system is 37% faster and now uses large stack.

Brother, if you ain't using Gentoo then, please, run don't walk
to the nearest psycho ward.

Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

Farley Flud wrote this copyrighted missive and expects royalties:

> I just noticed that the C++ packages "imath" and "openexr" can both
> be built with an option called "large-stack."
>
> Presumably, large-stack allows objects to be allocated on the
> stack rather than the heap and this is much, much, much faster.

Actually, a few years ago I did a timing test allocating data on the heap
versus the stack, and the heap was pretty close in time.

There could be some wrinkles in the setup I had, but at the time the
result surprised me. Perhaps my test took up so much time that it masked
the stack/heap times.

> Thus, on Gentoo, I just added the "large-stack" option and the
> two above packages were automagically re-built to use the stack.

IIRC I encountered a geospatial (?) application that required a large
stack. Again, years and years ago so my memory is dim.

> I pity those poor distro lackeys that must accept their generic
> junk.

Ever header of ulimit?

> My Gentoo system is 37% faster and now uses large stack.
>
> Brother, if you ain't using Gentoo then, please, run don't walk
> to the nearest psycho ward.

Where we can talk with you through a glass partition.

> Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

My sentiment exactly. :-)

--
Tempt not a desperate man.
-- William Shakespeare, "Romeo and Juliet"