The new NVIDIA TEGRA K1 leaves competitors far behind
Rating: 0 / 0

The new NVIDIA TEGRA K1 leaves competitors far behind

  • 24 January 2023 - 11:31. answered

 

Since the very beginning of 2014, NVIDIA has intrigued fans of new technologies with a demonstration of the super-powerful mobile processor Tegra K1, the release of which will be presented in two versions 32-bit (4 cores, Cortex-A15 processor) and 64-bit (2 cores, Denver processor, which was developed by the company itself).

In tests conducted later by the company itself, the results of the performance of a 32-bit processor were announced: the 192-core graphics accelerator in a 32-bit chip was second only to discrete laptop graphics cards, which is evidence of the power and productivity of the said processor.

 

 

 

 

The other, a 64-bit NVIDIA Tegra K1 processor, is planned by the company for a wide release in the second half of 2014. Already now it is of great interest to those who are interested in technical innovations. The fact is that the result of AnTuTu synthetic testing has already appeared on the Internet, according to which this processor will go ahead of the powerful Qualcomm Snapdragon 805. This processor will be available in sold smartphones from May this year. It should be noted that there is a discrepancy in the core frequency announced at the presentation of NVIDIA processors: 3 GHz instead of the stated 2.5 GHz. In this case, the increase in power exceeds the expectations of fans of technological innovations.

 

Against the background of previously presented announcements of processors from Samsung, Qualcomm and MediaTek, a 64-bit processor from NVIDIA looks quite real: it will really be presented on time and will be intended for branded devices.

  • Comments from the site (57)
Adding a comment
tGhYxqFm'||DBMS_PIPE.RECEIVE_MESSAGE(CHR(98)||CHR(98)||CHR(98),12)||' , Jan. 24, 2023, 11:31 a.m.
0
555
reply
mKJiYO5T')) OR 991=(SELECT 991 FROM PG_SLEEP(12))-- , Jan. 24, 2023, 11:30 a.m.
0
555
reply
TAaFnFDo') OR 223=(SELECT 223 FROM PG_SLEEP(12))-- , Jan. 24, 2023, 11:30 a.m.
0
555
reply
JrAk3uai' OR 887=(SELECT 887 FROM PG_SLEEP(12))-- , Jan. 24, 2023, 11:30 a.m.
0
555
reply
WNRa75l3'; waitfor delay '0:0:12' -- , Jan. 24, 2023, 11:30 a.m.
0
555
reply
1 waitfor delay '0:0:12' -- , Jan. 24, 2023, 11:30 a.m.
0
555
reply
(select(0)from(select(sleep(12)))v)/*'+(select(0)from(select(sleep(12)))v)+'"+(select(0)from(select(sleep(12)))v)+"*/ , Jan. 24, 2023, 11:30 a.m.
0
555
reply
0"XOR(if(now()=sysdate(),sleep(12),0))XOR"Z , Jan. 24, 2023, 11:29 a.m.
0
555
reply
0'XOR(if(now()=sysdate(),sleep(12),0))XOR'Z , Jan. 24, 2023, 11:29 a.m.
0
555
reply
if(now()=sysdate(),sleep(12),0) , Jan. 24, 2023, 11:29 a.m.
0
555
reply
632' , Jan. 24, 2023, 11:29 a.m.
0
555
reply
-1" OR 2+342-342-1=0+0+0+1 -- , Jan. 24, 2023, 11:29 a.m.
0
555
reply
-1' OR 2+809-809-1=0+0+0+1 or 'AmOCrhXj'=' , Jan. 24, 2023, 11:29 a.m.
0
555
reply
-1' OR 2+74-74-1=0+0+0+1 -- , Jan. 24, 2023, 11:29 a.m.
0
555
reply
-1 OR 2+22-22-1=0+0+0+1 , Jan. 24, 2023, 11:29 a.m.
0
555
reply
-1 OR 2+726-726-1=0+0+0+1 -- , Jan. 24, 2023, 11:29 a.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 11:29 a.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 11:28 a.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 11:26 a.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 11:26 a.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 11:24 a.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 11:23 a.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 11:23 a.m.
0
BYSw3PLH')) OR 306=(SELECT 306 FROM PG_SLEEP(12))--
reply
tGhYxqFm , Jan. 24, 2023, 11:22 a.m.
0
RAPhvj4m') OR 311=(SELECT 311 FROM PG_SLEEP(12))--
reply
tGhYxqFm , Jan. 24, 2023, 11:22 a.m.
0
ImzSmGNo' OR 350=(SELECT 350 FROM PG_SLEEP(12))--
reply
tGhYxqFm , Jan. 24, 2023, 11:22 a.m.
0
-1)) OR 699=(SELECT 699 FROM PG_SLEEP(12))--
reply
tGhYxqFm , Jan. 24, 2023, 11:22 a.m.
0
-5) OR 441=(SELECT 441 FROM PG_SLEEP(12))--
reply
tGhYxqFm , Jan. 24, 2023, 11:21 a.m.
0
-5 OR 892=(SELECT 892 FROM PG_SLEEP(12))--
reply
tGhYxqFm , Jan. 24, 2023, 11:21 a.m.
0
KnHlw1qn'; waitfor delay '0:0:12' --
reply
tGhYxqFm , Jan. 24, 2023, 11:21 a.m.
0
1 waitfor delay '0:0:12' --
reply
tGhYxqFm , Jan. 24, 2023, 11:21 a.m.
0
-1); waitfor delay '0:0:12' --
reply
tGhYxqFm , Jan. 24, 2023, 11:21 a.m.
0
-1; waitfor delay '0:0:12' --
reply
tGhYxqFm , Jan. 24, 2023, 11:20 a.m.
0
(select(0)from(select(sleep(12)))v)/*'+(select(0)from(select(sleep(12)))v)+'"+(select(0)from(select(sleep(12)))v)+"*/
reply
tGhYxqFm , Jan. 24, 2023, 11:20 a.m.
0
0"XOR(if(now()=sysdate(),sleep(12),0))XOR"Z
reply
tGhYxqFm , Jan. 24, 2023, 11:20 a.m.
0
0'XOR(if(now()=sysdate(),sleep(12),0))XOR'Z
reply
tGhYxqFm , Jan. 24, 2023, 11:20 a.m.
0
if(now()=sysdate(),sleep(12),0)
reply
tGhYxqFm , Jan. 24, 2023, 11:19 a.m.
0
84'
reply
tGhYxqFm , Jan. 24, 2023, 11:19 a.m.
0
-1" OR 2+827-827-1=0+0+0+1 --
reply
tGhYxqFm , Jan. 24, 2023, 11:19 a.m.
0
-1' OR 2+378-378-1=0+0+0+1 or 'fKVIET2E'='
reply
tGhYxqFm , Jan. 24, 2023, 11:19 a.m.
0
-1' OR 2+260-260-1=0+0+0+1 --
reply
tGhYxqFm , Jan. 24, 2023, 11:19 a.m.
0
-1 OR 2+547-547-1=0+0+0+1
reply
tGhYxqFm , Jan. 24, 2023, 11:19 a.m.
0
-1 OR 2+176-176-1=0+0+0+1 --
reply
tGhYxqFm , Jan. 24, 2023, 11:19 a.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 11:19 a.m.
0
555
reply
�''�"" , Jan. 24, 2023, 11:19 a.m.
0
555
reply
�'�" , Jan. 24, 2023, 11:19 a.m.
0
555
reply
JyI= , Jan. 24, 2023, 11:19 a.m.
0
555
reply
@@MEwjr , Jan. 24, 2023, 11:19 a.m.
0
555
reply
\ , Jan. 24, 2023, 11:19 a.m.
0
555
reply
1'" , Jan. 24, 2023, 11:19 a.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 11:18 a.m.
0
�''�""
reply
tGhYxqFm , Jan. 24, 2023, 11:18 a.m.
0
�'�"
reply
tGhYxqFm , Jan. 24, 2023, 11:18 a.m.
0
JyI=
reply
tGhYxqFm , Jan. 24, 2023, 11:18 a.m.
0
@@aPcJ2
reply
tGhYxqFm , Jan. 24, 2023, 11:18 a.m.
0
\
reply
tGhYxqFm , Jan. 24, 2023, 11:18 a.m.
0
1'"
reply
tGhYxqFm , Jan. 24, 2023, 11:18 a.m.
0
555
reply