Reddit mentions: The best computer performance optimization books

Practically, you can use Swift for anything where you would use Objective-C, but there are a few situations you might use Objective-C and a few times you must Objective-C.

• If you need to call C code, you might choose to use Objective-C because you may find directly using Objective-C is easier than dealing with Swift's various Unsafe* APIs. Then, you can use Swift to interoperate with your Objective-C code if the rest of your app is in Swift.
  
• Objective-C can outperform Swift significantly. Not only in terms of compilation speed but in terms of runtime performance. For instance, the book iOS and macOS Performance Tuning ( https://www.amazon.com/iOS-macOS-Performance-Tuning-Objective-C/dp/0321842847 ) gives some concrete examples. Of course, it depends on your code and where the hotspots are, so you need to measure performance. Swift can be faster than Objective-C, but there are situations where idiomatic Objective-C is naturally faster than idiomatic Swift. However, if you ever find yourself in a situation where you think Swift itself is slow, I would watch some of the WWDC talks regarding Swift performance to try to improve your Swift code before even thinking about re-writing it in C or Objective-C.
  
• A very few Apple APIs are still only accessible via Objective-C (e.g. Activity Tracing, XPC, some of the very low level audio frameworks). You'll usually know it when you try to read the headers for the function/method in Xcode (which are more up to date than the online docs) and the auto-generated Swift header doesn't make any sense .
  
  However even with the above, Swift is a better choice for new development. Apple has decided Swift is the future and is heavily investing in it. Performance is improving with Swift, the language is generally source code compatible for the last two years at least, and every year, more of the few remaining Objective-C only APIs have a Swift overlay.

Zen of Code Optimization

It's dated, but still fun to read and still provides a good mindset. I've owned this book for 20 years now, and I still flip through it every couple of years.

Webpagetest.org is the original web performance tool and it's opensource so you can poke around. Also, buy this book about WPT. It should be super eye opening... https://www.amazon.com/Using-WebPageTest-Performance-Testing-Novices/dp/1491902590

Depending on how skilled you are at Java:

• Effective Java
  
• Java Concurrency in Practice
  
• Java Generics
  
  Then for Android specifically:
  
  
• Efficient Android Threading
  
• Android Concurrency
  
• High Performance Android Apps
  
• Android Databases Best Practices
  

It happens. From what I understand mostly when a site grows and paying for optimization is cheaper than buying new servers (I probably should have said x86 instead of PCs)

This is the only source I found before I got bored searching XD http://www.amazon.com/Visual-C-Optimization-Assembly-Code/dp/193176932X

His algorithm reminds me of the one described by Michael Abrash in Zen of Code Optimization. It was a word counting program that IIRC processed the input in vectorized way (4 bytes at a time).

if you're really worried about efficiency you might want to check iOS and macOS Performance Tuning. As everyone else said, there's very little relation between lines of code and performance. If you're getting an awful performance in your app it might be due to methods messing with other threads or poorly designed repetitive tasks.