5 ms·
Very nice. I think the whole art of dealing with limited resources are lost on new programmers who have gigabytes of rams and gigacycles of compute. I love the
by ChuckMcM 9y ago
Very nice. I think the whole art of dealing with limited resources are lost on new programmers who have gigabytes of rams and gigacycles of compute. I love the old 1K demos for that reason, it really puts the puzzle back into programming.
In my experience, if you are familiar with RTL level synthesis of hardware then microprogramming isn't a huge leap (to me they feel very similar).
- pishpash 9y agoProgrammers should have machines worse than the users. Flame away.
- ChuckMcM 9y agoAlways a controversial position :-) Back in the day hosting the full development environment would often level out the differences in performance, not as much today. With mobile development you don't have much of a choice, your stuff has to run on the phone.
- pjmlp 9y agoIt still holds though, when developers get to only test on Google Pixie and Samsung S8, while customers are on ZTE Blade, the stuff might even install, but run it won't.
- bluedino 9y agoAt least for testing. My favorite example was the Microsoft Office for Mac team testing every build on a 6100/60
- dingo_bat 9y agoFor testing/debugging, yes. For compiling, no.
- krylon 9y agoI like to have a decent machine for development, especially when running Visual Studio (which I do not use often, but Visual Studio is not exactly lightweight). But for testing I absolutely prefer to use a low-end machine. I used to have a SparcStation 20 at home (it died a few years ago, though), and I loved that machine for that precise reason. (Also: Big-endian vs. Little-endian issues) Damn, that beast was SLOW. Not just slow: It only had 64 MB of RAM, and I had removed the hard drive because it was way too loud, so the entire thing ran over the network. Swapping over a half-duplex 10MBit line makes you really think about memory usage. ;-)
- AceJohnny2 9y ago> I think the whole art of dealing with limited resources are lost on new programmers who have gigabytes of rams and gigacycles of compute. Chuck, people have been saying that since punch-card days. And here I am, cutting out strings from my program to make it fit under the 1MB barrier for my bootloader-to-SRAM to be happy :)
- ChuckMcM 9y agoNo doubt true. I still think it makes programming more interesting if it is constrained.
- specialist 9y agoConstraints make a lot of creative endeavors interesting. I have no idea why Lego modeling is so compelling when you can just print miniatures, but for me looking at people's work is like crack.
- Retra 9y agoYou're just solving the wrong problems then. Try rendering the whole Earth at sub-cm resolution or something. There are so many things we can't do right now because we're too constrained...
- digi_owl 9y agoI think he is more railing against text editors made using JS and a chrome-less web browser...
- jacobolus 9y agoYou just need to solve more computationally intensive problems. There are plenty of simulations and mathematical graphics you can make which take hours of rendering time on a fast modern machine, where optimizing the inner loops can have a big impact.
- tetha 9y agoI've made java services respond with 500us on average for in-memory queries. Yeah, average, including GC stops. This is where things grow really fun, because every lock, every array access, every method call becomes a problem. It's an interesting world. Closed and not entirely relevant to most developers.
- Bjartr 9y agoWhat are good, up to date resources for performance tuning to that degree in Java? I've looked into this a few times and keep hitting walls where the resources I have found say "let the JVM do it's thing".
- wpietri 9y agoThis mailing list is amazing: https://groups.google.com/forum/#!forum/mechanical-sympathy https://groups.google.com/forum/#!forum/mechanical-sympathy I understand maybe a third of it, but what I do get is high quality.
- tetha 9y agoMechanical sympathy is a good source, probably the source for java specific topics. In general, you'll want to really, really learn the internals of the JIT so you can structure your application to cooperate with the JIT and the GC. Beyond that, I've found the biggest throughput gains and/or latency decreases by implementing the right threading or lack of threading, locking or lock-free implementations, and then tuning, profiling and optimizing things just right for the target hardware. That's just a little sentence, but it's an amazingly hard topic. There are not many resources about this out there beyond just looking at high performance systems, regardless of language. The innodb storage engine is a fun project with some interesting locking, and I like reading about the things the kernel does.
- pjmlp 9y agoBesides what the others pointed out, check profilers like VisualVM, ControlCenter, Netbeans integrated one. There is also the option to get the generated machine code, here is a recent example with the Oracle JDK about SIMD programming in Java. http://prestodb.rocks/code/simd/ http://prestodb.rocks/code/simd/ Finally, note that just like many programming languages, Java enjoys multiple implementations, each with its own JIT.