

The screen shouldn't have to redraw multiple times, Internet-loaded content shouldn't have to update, and so on. That's because iOS correctly assumes that you're most likely to return to them, and it wants to give you the best experience when you do. However, the next few apps in the App Switcher may also be consuming some CPU and memory resources. That's sensible - the performance of that app is paramount.

In normal usage, iOS devotes the lion's share of CPU and memory resources to the app that you're using. They're much more like the contents of the Mac's Apple > Recent Items menu. It's difficult to count apps in the App Switcher, but I probably have at least a hundred in there.) As the number of apps in the App Switcher should indicate, those apps are not necessarily running - they merely have run at some point in the past. (The very first app in my iPhone 11 Pro's App Switcher is Apple's Tips, which I think came up automatically when I turned the iPhone on last year and hasn't been touched since. When you invoke the App Switcher in iOS, you can swipe right to see all the apps you've used, possibly since you got your device.

No one, possibly short of an iOS systems engineer armed with Apple's internal diagnostic and debugging tools, would be able to outguess iOS itself on issues like memory usage, power draw, and CPU throttling. Apple has put a great deal of effort into ensuring that iOS knows the best ways to manage the limited hardware resources within your iPhone or iPad. Why would these behaviors reduce battery life? Remember, iOS is a modern operating system that's built on top of Apple's proprietary hardware. The router automatically enters in computer names and their IP address into its local DNS service at the same time as it hands out DHCP addresses and also since it is the router it also sees computer names of all devices talking to the Internet so it's able to build a local DNS database.Adam Engst, writing for TidBITS: Because force-quitting apps and restarting or shutting down devices are necessary only to fix unanticipated problems, there are two notable downsides to engaging in such behavior as a matter of habit: reduced battery life and wasted time. The reason the router would know the IP address for other devices on your local network is because it is also the DHCP server for your LAN. You know things in your LAN that are typically 192.168.1.x or something like that. But if you change the DNS server to use at the computer then when you need the IP address for that other computer name on your local network then the Internet DNS server that you are using is going to be used and it won't know a thing about your internal network and what IP address anything is on your LAN. When configured properly if your computer needs the IP address for an Internet resource it asks the local DNS server (your router) and your router then forwards this request to either the ISP DNS or to some other DNS server if you've changed it at the router. When you set your computer's DNS to be 8.8.8.8 and 8.8.4.4 you have removed your computer's ability to resolve IP addresses for your local LAN of other devices on your LAN. You'll get better WiFi and a better firewall and your local network resources will be accessible and fast. But changing Internet DNS servers is something that needs to be done only at the router (on a home network).īuy your own router so that you can do this and more easily the right way. That is because ISP's default DNS servers are unreliable and slow.
