Transmeta Crusoe TM-5800

Le Transmeta Crusoe TM5800 est un processeur très peu puissant (un des moins puissants actuellement). Le CPU 128-Bit VILV (Very Large Instruction Word) est plus simple qu'un processeur x86 (32bits). Avec le Code Morphing, le TM-5800 peu émule les instructions x86+MMX matérielles.

Gamme	Transmeta Crusoe
Nom de code	Crusoe
Fréquence	1000 MHz
Bus système	266
Cache de Niveau 1 (L1)	128 KB
Cache de Niveau 2 (L2)	512 KB
Nombres de cœurs/threads simultanés supportés	1 / 1
Consommation énergétique maximale (TDP)	7 Watt(s)
Nombre de transistors	36.8 Million(s)
Fonctionnalités	130 nm1.4/0.8V
Taille du Die	55 mm²
Socket	CBGA-474
Fonctionnalités	MMX, LongRun
Architecture	x86
Date de présentation	06/01/2001

Benchmarks

wPrime 2.10 - wPrime 2.0 32m *

497 s (100%)

+ 1 Plus de détails + Montrer le tableau de comparaison

Modèle	Processeur	Carte graphique	RAM	Valeur
	TM-5800			497

Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *

276.8 s (60%)

+ 1 Plus de détails + Montrer le tableau de comparaison

Modèle	Processeur	Carte graphique	RAM	Valeur
	TM-5800			276.8

SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)

2368 MIPS (1%)

+ 1 Plus de détails + Montrer le tableau de comparaison

Modèle	Processeur	Carte graphique	RAM	Valeur
	TM-5800			2368

SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)

606 MFLOPS (0%)

+ 1 Plus de détails + Montrer le tableau de comparaison

Modèle	Processeur	Carte graphique	RAM	Valeur
	TM-5800			606

PCMark 04 - PCMark 04 - Standard

963 Points (13%)

+ 1 Plus de détails + Montrer le tableau de comparaison

Modèle	Processeur	Carte graphique	RAM	Valeur
Dialogue Flybook A33i	TM-5800	Mobility Radeon M6 0 GB	0.5 GB	963

- Amplitude des valeurs obtenues dans le benchmark avec cette carte graphique

- Valeur moyenne obtenue dans le benchmark avec cette carte graphique
* Plus les chiffres sont petits, plus les performances sont élevées

v1.17

log 15. 19:43:44

#0 no ids found in url (should be separated by "_") +0s ... 0s

#1 not redirecting to Ajax server +0s ... 0s

#2 did not recreate cache, as it is less than 5 days old! Created at Thu, 12 May 2022 10:17:23 +0200 +0s ... 0s

#3 linkCache_getLink no uid found +0.002s ... 0.003s

#4 composed specs +0s ... 0.003s

#5 did output specs +0s ... 0.003s

#6 getting avg benchmarks for device 225 +0.001s ... 0.004s

#7 got single benchmarks 225 +0.005s ... 0.009s

#8 got avg benchmarks for devices +0s ... 0.009s

#9 linkCache_getLink no uid found +0.001s ... 0.01s

#10 linkCache_getLink no uid found +0.002s ... 0.012s

#11 linkCache_getLink no uid found +0s ... 0.012s

#12 linkCache_getLink no uid found +0s ... 0.013s

#13 linkCache_getLink no uid found +0s ... 0.013s

#14 linkCache_getLink no uid found +0s ... 0.013s

#15 linkCache_getLink no uid found +0s ... 0.013s

#16 linkCache_getLink no uid found +0s ... 0.013s

#17 linkCache_getLink no uid found +0.006s ... 0.018s

#18 linkCache_getLink no uid found +0.002s ... 0.02s

#19 linkCache_getLink no uid found +0s ... 0.02s

#20 linkCache_getLink no uid found +0s ... 0.021s

#21 linkCache_getLink no uid found +0s ... 0.021s

#22 linkCache_getLink no uid found +0s ... 0.021s

#23 linkCache_getLink no uid found +0s ... 0.021s

#24 linkCache_getLink no uid found +0.001s ... 0.022s

#25 linkCache_getLink no uid found +0.001s ... 0.023s

#26 linkCache_getLink no uid found +0s ... 0.023s

#27 linkCache_getLink no uid found +0s ... 0.023s

#28 linkCache_getLink no uid found +0s ... 0.023s

#29 linkCache_getLink no uid found +0.002s ... 0.025s

#30 linkCache_getLink no uid found +0.001s ... 0.026s

#31 linkCache_getLink no uid found +0s ... 0.026s

#32 linkCache_getLink no uid found +0s ... 0.027s

#33 linkCache_getLink no uid found +0s ... 0.027s

#34 linkCache_getLink no uid found +0s ... 0.027s

#35 linkCache_getLink no uid found +0.001s ... 0.028s

#36 linkCache_getLink no uid found +0s ... 0.028s

#37 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.028s

#38 linkCache_getLink no uid found +0s ... 0.028s

#39 linkCache_getLink no uid found +0s ... 0.028s

#40 linkCache_getLink no uid found +0s ... 0.028s

#41 linkCache_getLink no uid found +0s ... 0.028s

#42 linkCache_getLink no uid found +0.001s ... 0.029s

#43 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.03s

#44 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.03s

#45 linkCache_getLink no uid found +0s ... 0.03s

#46 linkCache_getLink no uid found +0s ... 0.03s

#47 linkCache_getLink no uid found +0.001s ... 0.031s

#48 linkCache_getLink no uid found +0s ... 0.031s

#49 linkCache_getLink no uid found +0s ... 0.031s

#50 linkCache_getLink no uid found +0s ... 0.031s

#51 linkCache_getLink no uid found +0s ... 0.031s

#52 linkCache_getLink no uid found +0s ... 0.031s

#53 linkCache_getLink no uid found +0s ... 0.031s

#54 linkCache_getLink no uid found +0s ... 0.031s

#55 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

#56 linkCache_getLink no uid found +0.001s ... 0.033s

#57 linkCache_getLink no uid found +0.001s ... 0.033s

#58 linkCache_getLink no uid found +0s ... 0.033s

#59 linkCache_getLink no uid found +0s ... 0.034s

#60 linkCache_getLink no uid found +0s ... 0.034s

#61 linkCache_getLink no uid found +0s ... 0.034s

#62 linkCache_getLink no uid found +0s ... 0.034s

#63 linkCache_getLink no uid found +0s ... 0.034s

#64 linkCache_getLink no uid found +0s ... 0.034s

#65 linkCache_getLink no uid found +0s ... 0.034s

#66 min, max, avg, median took s +0s ... 0.034s

#67 no comparison url found in template nbc.compare_page_2 needed +0s ... 0.034s

#68 return log +0s ... 0.034s

:: Aucune critique trouvée pour ce processeur (pour le moment).

Please share our article, every link counts!

Transmeta Crusoe TM-5800

Benchmarks

Les autres processeurs de la gamme Crusoe

Processeurs similaires