Intel shares its future plans: Are the new processors worth the wait?

3 mins read
Intel shares its future plans: Are the new processors worth the wait?

Attending a symposium today, Intel talked about its 14th generation Meteor Lake processors, their power consumption and performance.

Intel shares its future plans: Are the new processors worth the wait?

Although Intel has not yet released its 13th generation processors, it shared some information about the Meteor Lake (14th generation) family at a symposium it attended today. What attracted the most attention was that although it had the same TDP (power consumption) values as its predecessors, it was able to reach higher clock speeds. So how did Intel achieve this?

14th generation Intel Meteor Lake processors show great promise!
14th generation Intel Meteor Lake processors are not on the agenda for the time being. Because the introduction of the 13th generation is expected in the coming months. Moreover, on the power consumption side, Intel has big promises. However, the company is already sharing that it plans to continue the important steps it has taken in this area and what the next series will offer us.

Speaking at the symposium, the company made some statements about the Intel 4 (7 nm) processing node. As the next generation of Intel 7 (10 nm Alder Lake and Raptor Lake), it will come with a new socket and architecture, he said. It is stated that the power consumption values will be quite similar to the 12th generation, but the performance will reach much higher levels.

When we look at the shared numbers, we will see clock frequencies up to 21.5 percent higher at the same power consumption values than the Intel 7 series. If we think about it in the opposite way, in a test environment where it gives the same performance, the Meteor Lake series will consume 40 percent less power than its predecessor. It is stated that they have achieved this with improvements of up to 2 times in areas such as field scaling and improvements in chip architecture.

In addition, the new chips will use Intel’s Foveros 3D technology. It will also have a four-mold setup that is combined with TSV connections. In the light of all these developments, the system is said to be grouped under 4 different roofs. In addition, thanks to the new architecture, it is stated that the process steps are shortened by 5 to 20 percent on the production side.

The company shared some information about not only Intel 4, but also Intel 3 process. For example, it was said that I3 would be about 18 percent faster than I4, and that I3 would switch to nodes 20A and 18A. However, it was stated that these are preliminary estimates and that the products to be released to the market may give different results (probably in a positive sense).

What do you think about this? Don’t forget to share your opinions with us in the comments!

 

FİKRİKADİM

The ancient idea tries to provide the most accurate information to its readers in all the content it publishes.


Fatal error: Uncaught TypeError: fclose(): Argument #1 ($stream) must be of type resource, bool given in /home/fikrikadim/public_html/wp-content/plugins/wp-super-cache/wp-cache-phase2.php:2386 Stack trace: #0 /home/fikrikadim/public_html/wp-content/plugins/wp-super-cache/wp-cache-phase2.php(2386): fclose(false) #1 /home/fikrikadim/public_html/wp-content/plugins/wp-super-cache/wp-cache-phase2.php(2146): wp_cache_get_ob('<!DOCTYPE html>...') #2 [internal function]: wp_cache_ob_callback('<!DOCTYPE html>...', 9) #3 /home/fikrikadim/public_html/wp-includes/functions.php(5420): ob_end_flush() #4 /home/fikrikadim/public_html/wp-includes/class-wp-hook.php(324): wp_ob_end_flush_all('') #5 /home/fikrikadim/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array) #6 /home/fikrikadim/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #7 /home/fikrikadim/public_html/wp-includes/load.php(1270): do_action('shutdown') #8 [internal function]: shutdown_action_hook() #9 {main} thrown in /home/fikrikadim/public_html/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 2386