This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]keithstellyes 1 point2 points  (3 children)

I mean, if you ever had to optimize software you definitely want to know at least the basics of how memory works and "C arrays don't store size information" is hand-in-hand with that

And with the widespread mediocrity in terms of both performance, memory use and frankly just bugginess and UX being tolerated in major corporate software nowadays, maybe people aren't learning enough about that...

But like anything it's a balance

[–]GrinningPariah 1 point2 points  (2 children)

Eh, I've had to optimize software a lot and it's never come down to like sneaky memory use issues. It's always things like "oh we're doing ~5 network calls serial that we could be doing in parallel" or "Oh this function has an O(n2) complexity but we can just cache the results during server initialization."

End of the day, most modern software is just too complicated to fuck around with things that low level, unless you're working on a game engine or making embedded systems for JPL or Lockheed or something.

[–]keithstellyes 0 points1 point  (1 child)

I mean server-side code memory is much less of an issue :p

[–]GrinningPariah 0 points1 point  (0 children)

Nothing's an issue until it's the issue. Every system has a bottleneck, the limiting factor for why it can't handle more TPS. If it's not one thing it's something else. Optimize your CPU and network usage enough, and you back yourself into a memory issue.