Showing posts with label no. Show all posts
Showing posts with label no. Show all posts

More cores more power and still no effective cooling system

| 0 comments |

I think we really have a problem here. Watching the world of technology, there is a clear tendency to equip mobile devices with more and more power. Looking at the specifications of fleshly unveiled Nvidia Tegra 4 (72 custom Nvidia GeForce GPU cores, new quad-core variant of ARMs Cortex-A15 CPU) I can say Im already pretty amazed. But this enthusiasm might be suppressed very soon!

Where is the issue? You might say weve already been there few years ago, when multi-cores CPUs were gaining more and more attention from non-professional desktops/notebooks users. Marketing did a great job then. Nobody cared that most of consumers wouldnt be able to use the power of multi-cores. Nobody told them, that powerful CPU in pair with 1 GB of RAM memory and 5.400 RPM hard drive will be a waste of money and power. But its not the point here.

What matters is the method of heat extraction. Air or water cooling systems are very advanced these days and can be very effective when it comes to PC. So if you really want to use 4 cores CPU for MS Word Editing or Internet browsing on your PC, there is nobody stopping you, apart of your own pocket. But what about mobile phones, tablets or so popular these days ultrabooks? Cooling systems on those devices are really bad. And what makes it even worse, there is no revolution coming. At least not for mobile phones or tablets.

Most of new ultrabooks (equipped with powerful CPUs and dedicated GPU) suffers from so called "throttling", caused by too much heat generated by the CPU and GPU when under heavy load together. Extra thin constructions are not effective when it comes to cooling, because the size of cooling heaps and fans needs to be reduced to minimum. Of course there is some room for improvements. For example, in  new MacBook Pro you can find two fans and quite smart arrangement of cooling pipes. Notebooks/ultrabooks designers surely have more options and more space than mobile phones designers. So I believe this might get better in time.

Whats the situation when it comes to mobile phones? As I mentioned before, I think its really bad. First of all, you cant put any fan inside your phone. The space inside is so limited, so forget about advanced system of micro cooling pipes. So what is the current solution? For example, idea of 5th companion core presented by Nvidia in Tegra 3. When device is in idle state, 5th core is taking care of low level tasks, running at very low frequency. Yes, this is quite smart. Tegra 4 will have the same mechanism. Another example - smart governors. When you turn your screen off, you CPU frequency will be limited to lets say 340 MHz. When turning screen on, it will go back to lets say 1,7 GHz. Nice, huh?

So... wait a minute!

It seems that from one hand we are buying super powerful devices, and from the other hand there are plenty of methods to limit this power. People are happy these days when they can use their super phone for more then 16 hours without charging. They do everything to achieve that - they are limiting GPU power, CPU power, turning off capacitive buttons lights or changing screen backlight to minimum (and they can barely see whats written on the screen). So take a moment, sit on the chair and count - how many times have you actually used the power of your device? Do you really need 4 cores and 2GB of RAM for Gmail, Chrome or Andry Birds? I dont think so. You might say you are playing heavy 3D games. Okay - how long can you play Need For Speed on your device in the bus? Im pretty sure your device will be discharged after less then 1 hour. So, you might say you can always play it at home, with a device connected to the charger. Personally, when sitting home I prefer playing Need For Speed on PC or notebook.

Whats the point in having 4 cores CPU, 2GB RAM and 72 custom Nvidia GeForce GPU cores if you cant use it? In idle this will be limited to 1 hidden core running something like 70 MHz. When using the phone for daily tasks (photos, internet, mail, calling) it will use about 20% of the potential power. When playing games it might use the full power for some period of time, then will be down-clocked because of generated heat. Is it comfortable to hold a device in your hand that have a temperature of 59 °C? I dont think so...
Of course there is a matter of reducing the size of the chipsets. Newer production processes mean lower power consumption. But this wont help.

So is it a right and good direction, when a companies are making more and more powerful hardware, trying to figure out better and more effective way to limit this power at the same time? Its like putting in and out. And all for the money from customers.

Do you have any questions or comments? Feel free to share! Also, if you like this article, please use media sharing buttons (Twitter, G+, Facebook) below this post!


For latest news follow Android Revolution HD on popular social platforms:

Read More..

No map is an island Introducing a connected JavaScript Maps API experience

| 0 comments |
Cross-posted from the Google Geo Developers blog

Our digital lives are increasingly connected. We research on our laptops, look up directions on our phones and even navigate with our watches. And by creating maps unique to each user and offering features such as saved places, Google Maps has been making it easier to continue these tasks as we move from device to device.

However, although maps embedded from Google Maps are now built uniquely for every Google user, most of the now two million active sites and apps using the Maps APIs are still islands. When I look for a place to eat on Zagat, I can’t see how far away it is from work. When I look at a travel map in the New York Times, I can’t save those places in order to navigate to them later.

Today we’re taking a step towards connecting these two million sites and apps by introducing a signed-in JavaScript Maps API experience and a feature called attributed save. To help illustrate, we’ve partnered with the New York Times to bring this experience to their 36 hours travel column.

A connected JavaScript Maps API

When you add &signed_in=true to the Google Maps JavaScript API source url, your end users will have the option to sign into the map with their Google account. When they do so, your users will receive a map built for them, in the context of your app. Their saved places — including home and work addresses (if set by the end user) as well as other relevant places — will appear automatically on their map, providing a layer of context that anchors your content and makes it stand out even more.

Attributed save

Once users are signed into the Google Maps in your app, we can together create an integrated experience between your map content and Google Maps. With attributed save, signed-in users can save places from your app to be accessed later, with attribution and linkbacks, on Google Maps for the web, Android and iOS.

What’s more, you can also enable deep links into your mobile applications. For instance, users can save a place from your desktop app (such as Zagat.com), open up the place on Google Maps on their Android device, and deep link directly into your Android app.

Enabling attributed save is easy — just specify your app name, a link and a place search string or place ID when creating a marker and info window. Or use our SaveWidget to enable attributed save in your own custom info window.

In addition, we’re also launching attributed save across all embedded maps today. Attribution and linkback parameter will be inferred automatically from the domain and referrer of the host site, so if you’re using our embedded maps, you don’t need to do anything! If you’re using the Google Maps Embed API, you may customize the source and link back parameters yourself.

One final point: we’ve stated in the past that the JavaScript Maps API is cookieless if loaded from maps.googleapis.com. As of today, to enable the signed in maps experience on sites across the web, the signed-in version of the JavaScript Maps API now does rely on cookies to detect the end user’s signed-in state. Please review our documentation for further details.

That’s all for now. Go try it out. And remember, no map is an island, entire of itself...

Read More..