387 FPU Math CoProcessor Benchmarks & Comparison / Intel, Cyrix, IIT, Chips & ULSI

  Рет қаралды 38,341

CPU Galaxy

CPU Galaxy

3 жыл бұрын

In this video I will explain a bit about the 387 math coprocessor and for which applications it might be usfull. Byside that you can see here some nice benchmarks and comparison from different FPUs as Intel, Cyrix, IIT and Chips & Technology. At the end of the video you can see a small part of the legendary Crystal Dreams 2 Demo made by Triton.
Download here the charts you saw in the video:
www.cpu-galaxy.at/download/38...
Wikipedia IEEE Floating Point Standard:
en.wikipedia.org/wiki/IEEE_754
Wikipedia Floating Point Unit
en.wikipedia.org/wiki/Floatin...
Used benchmark programms and links:
DR-Hard 3.0
www.drhardware.de/pghgretro.htm
Fractint 20.0
archive.org/details/frain200
FPUbench (was not considered in the rating)
old-dos.ru/index.php?page=file...
Thanks for watching.
If you want to donate or support this channel:
paypal.me/cpugalaxy
If you want to donate material or getting in touch with me just
comment below or send me an email: cpugalaxy@gmx.at
Find me also on cpugalaxy

Пікірлер: 368
@cabasse_music
@cabasse_music 3 жыл бұрын
do you have a rapidcad? i'm curious where that would fall between the 386 and 486
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Yes, I have the Intel Rapid Cad as well. There will be a follow up video with benchmarks where I will compare the 386+387, Intel Rapid Cad and the 486 @ 33 MHz. 😀
@lazibayer
@lazibayer 3 жыл бұрын
@@CPUGalaxy Would you include other 386/486 hybrid chips such as 486dlc as well?
@pascalmathieu9332
@pascalmathieu9332 3 жыл бұрын
I've use a 386sx and a 486sx, both at 33Mhz, the 486 was as twice as fast in regular use . You can find on Internet the difference of cpu cycles needed for floating point operation on 386, 486, sx/dx. FP sofware emulation is slow on a 386, merly 50 cpu cycles and only 16 on 486.
@cabasse_music
@cabasse_music 3 жыл бұрын
@@pascalmathieu9332 if i understand correctly the RapidCad was actually a 486dx wired up to the socket layout for a 386, more or less, with the FPU inside the die and the second chip as merely a dummy for compatibility
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
The second chip is some logic chip which is redirecting the math co pro signals back to the cpu. this weekend in my next video I will review the RapidCAD
@SkyOctopus1
@SkyOctopus1 3 жыл бұрын
Oh the nostalgia. I did my PhD designing maths co-processor hardware. My rose-tinted glasses filter out the hideousness of having to design these things and now I can just appreciate the beauty in them.
@yalezhang8831
@yalezhang8831 3 жыл бұрын
I love computer architecture. How many cycles did your designs take for a multiply? Was it pipelined? What was the radix of the adders used for multiply? Does it handle denormals and the different IEEE rounding modes or nobody cared? I got the impression those are the bane for many designers. Multiprecision multipliers are becoming popular these days for use on CNNs. I don't know if that made sense back then.
@ernestuz
@ernestuz 3 жыл бұрын
At some point I was involved in CPU designs, and one of them brought me to some FPU work. Shifters, shifters, shifters and CORDIC! It's hypnotic to me see the final result, how zillions of Verilog lines end up in those marvellous geometries on the die.
@udirt
@udirt Ай бұрын
You must be a genius at that level... wonderful!
@matt.604
@matt.604 3 жыл бұрын
I remember in 1993ish when the AutoCAD ppl at work who were using older computers got upgraded with 387 co-pros. It was a glorious day.
@AndyMarsh
@AndyMarsh 3 жыл бұрын
I remember the day I got a 486 with a Matrox card for AutoCAD... Oh the joy of fast redraw!
@lazibayer
@lazibayer 3 жыл бұрын
Interesting to see that Cyrix nailed the fpu performance in the 387 era but got beaten up two generations later.
@MrKillswitch88
@MrKillswitch88 3 жыл бұрын
Good thing as they are cheap compared to some of the others be it for collecting or for a build.
@wishusknight3009
@wishusknight3009 3 жыл бұрын
Because they were basically using the same FPU 2 generations later..... Well, not quite. It was enhenced but on on their initial dx2 and dx4 cpu's the FPU was forced to run at bus clock. And on the 5x86 of socket 3 it ran at half cpu clock. It was still really strong for its actual clock speed but being disadvantaged by its low clocks.
@stefanmisch5272
@stefanmisch5272 3 жыл бұрын
Intel basically just got the FPU running according to spec whereas Cyrix hired mathematicians to optimize their FPU. Later on the FPU usage in FPS games was wildly underestimated bei Cyrix as well as AMD. AMD was able to rectify this with the Athlon which had a really strong FPU. Unfortunately, later they were betting on the APU and GPGPU for FP math rather than the integrated FPU in their bulldozer design. We know how that turned out ...
@wishusknight3009
@wishusknight3009 3 жыл бұрын
@@stefanmisch5272 Bulldozer was counting on games going wide threaded about 5 years before it started to really happen. It really had nothing to do with the GPGPU heterogeneity. It also suffered from chronic lateness to market, and a gross miss calculation about just how strong sandy bridge actually was. Bulldozer was intended to compete with Nahalam and not Sandy Bridge / Ivy bridge. In that world it would have been more than competitive against Gulftown and Clarkdale. AMD saw the writing on the wall pretty much the day the 2600K was launched and decided to throw everything, including the kitchen sink at a clean room proper strait up high performance core in zen. and only dedicated just enough resources to it to keep them from sinking, The interesting thing was all 5 (or 6?) iterations of APU's did see IPC increases each generation and refinements.. I would imagine had AMD not thrown the towl in, made use of more agressive process nodes and such, the performance class chips would have had the 10% IPC gains per year that AMD originally promised with it.. As Excavator saw... Keeping in mind that it was really only the second iteration, and the APU's went several after that... But in the end they really did make the right move. Lisa Su seems to know what she is doing. I am no bulldozer apologist, It was a day late and a dollar short, And as a result it really did suck if am honest. but I am fascinated with the vision they were going for. Bulldozer is actually still a decent gamer if you have an 8thread 8350 with some clock applied, it had as long of a useful life to those who bought it as the 2600K did. "It was ahead of its time".. lol
@lazibayer
@lazibayer 3 жыл бұрын
@@wishusknight3009 I still have a bulldozer machine built in 2016. Now it's 5yrs later but it's still slow as xxxk🤣
@legiran9261
@legiran9261 3 жыл бұрын
These chips were the Radeon Instinct MI 100 and Nvidia Tesla A100 from the late 80s / early 90s. Amazing how much this tech has progressed in 3 decades.
@bertholtappels1081
@bertholtappels1081 3 жыл бұрын
Finally this channel gets the traction that it deserves. All this content is incredibly interesting, and I’m not at all into collecting stuff. It’s just a superb way of explaining the fundamentals of micro architecture. (edit: typo) (edit 2: and what in the world is that EDM-meets-yodeling song? Googling Austria hits, yodel techno, etc. is going nowhere kzfaq.info/get/bejne/p8d3hNuLqr_GqWQ.html )
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
thank you. lol, this yodeling song is called „bring me edelweiss“ from 1983. 😉
@bertholtappels1081
@bertholtappels1081 3 жыл бұрын
@@CPUGalaxy Thanks for the ear worms, guys 🤨
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
lol. now I got the earworm as well 😂😂
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
😂
@freddyfredrickson
@freddyfredrickson 3 жыл бұрын
I remember all those advertisements for CPU with math coprocessor.
@OzirisTechnologies
@OzirisTechnologies 3 жыл бұрын
who knew that I would need to wait 30-ish years to see benchmarks regarding something I always questioned myself about. Thank you !
@PaulinesPastimes
@PaulinesPastimes 3 жыл бұрын
Oh how I wanted a co-processor for my 386 SX25 all those years ago. Now I know that my desire was warranted 😄. Excellent video 👍✨
@viniciusschneider705
@viniciusschneider705 3 жыл бұрын
Hey Pauline, do you like vintage hardware?
@brokengoose
@brokengoose 3 жыл бұрын
In early Pentium days, games started to require "486 or better", but they usually only needed a math coprocessor. By that time, 387s were very inexpensive and, most of the time, they were enough to allow 386s to run "486 or better" games.
@dycedargselderbrother5353
@dycedargselderbrother5353 3 жыл бұрын
Some of them did say "math co-processor required" but I imagine that was a more confusing sell than to just say "486 or better".
@cloerenjackson3699
@cloerenjackson3699 3 жыл бұрын
Awesome! I Nudged you for this maybe two months ago, thanks for doing it! It's a historically valuable video.
@ernestuz
@ernestuz 3 жыл бұрын
There was also in the days a very unusual brand, Weitek, their coprocessors were the fastest, but they didn't work as a x87 replacement, needing a special socket. In fact they were available for other CPU families as well. Also kudos to all those manufacturers that took the effort to implement IEEE 754 in hardware, it's quite a complex standard for 1985's technology. (EDIT: Oops, I have realized someone there is at least another comment on the matter)
@TheJeremyHolloway
@TheJeremyHolloway 3 жыл бұрын
I seem to recall WinChip and some other manufacturers that Best Buy and CompUSA/ComputerCity used to stock for older CPUs late in the day in 1999, in addition to Cyrix and other companies. FPUs probably could be used to improve decoding of music files. I recall on the Atari Falcon030 there was one MOD - or was it MP3? - player that could use the Motorola 68882 FPU to improve performance years after that computer was discontinued. I'm sure there's players on the Amiga that did the same...
@JohnHeritage
@JohnHeritage 3 жыл бұрын
Hooray for Crystal Dreams! Loved that demo!
@soniclab-cnc
@soniclab-cnc 3 жыл бұрын
I had to get the 387 for AutoCAD 1.0 . The difference really was impressive for my old i386. Drawing in 3D was so very slow without it....painfully so.
@MrMilli
@MrMilli 3 жыл бұрын
I remember MicroProse Grand Prix (GP1) speeding up when I installed a 387 on my Cyrix 386SX-16 computer back in the day. Might be an option for your 387 testing.
@TheJeremyHolloway
@TheJeremyHolloway 3 жыл бұрын
I'd really like to see a comprehensive list of pre-Pentium era games that used FPU co-processors. And also including games on the Amiga/Apple Mac/Atari ST that actually used the Motorola 68881 & 68882 FPUs...
@DanielLopez-up6os
@DanielLopez-up6os 3 жыл бұрын
The Co Processors were very much relic of their time, but theyre still AWESOME!
@pqrstzxerty1296
@pqrstzxerty1296 3 жыл бұрын
You do still get Co processors, but for cheapness they are just reprogrammed CPU's, we juat call them GPUs NPUs and APUs.
@soylentgreenb
@soylentgreenb 3 жыл бұрын
Integration is what makes technology cheap; what happened to FPUs happend to almost everything, steadily. It's been happening steadily from the very beginning of integrated circuits. Before there were CPUs built from a single chip, you could build a CPU from many chips where each chip had some small number of functions; e.g. some registers, or an adder, or logic operations, or adressed into a core memory plane. L1 cache used to be on the motherboard, then it was put into the CPU and L2 cache was put on the motherboard. FPUs used to be done in software, then there were coprocessors, then the coprocessor was put into the CPU. Then L2 cache was put into the CPU. Multiple CPUs used to live in multiple sockets on the same motherboard and then it was put into the CPU. RAM used to come as tiny DIP chips, dozens and dozens of them, then they were put into SIMMs and DIMMs and stuck on the motherboard. The memory controllers used to live in the north bridge on the motherboard, and then they were put inside the CPU. An early 8088 or 286 motherboard could do almost nothing and had an overwhelming number of chips on the motherboard. If you want a floppy drive; there's an ISA card for that. If you want a harddrive; there's an ISA card for that. If you want a scanner, there's an ISA card for that with a parallel port on it. If you want a mouse, there's an ISA card with serial port on it. 386DX-40 is when PC really started to become affordable. There were Maybe half a dozen chips plus some cache DIP modules; very highly integrated. If you wanted CDROM, harddrive, mouse and printer there was a single ISA card for that, that was fairly cheap. That's what made technology cheap; what made technology fast was Dennard scaling, not Moore's.
@user-7165jdhrnxymzn
@user-7165jdhrnxymzn 3 жыл бұрын
@@soylentgreenb 👌 thanx alot for your explanations , i really appreciate it 🙏
@diegodonofrio
@diegodonofrio 3 жыл бұрын
Your channel is very addictive 😍 Love your videos, thanks 😊
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Thank you!
@wishusknight3009
@wishusknight3009 3 жыл бұрын
I remember contemplating getting a Fasmath back in the early 90s when they started to get really cheap. I saw benchmarks of one being ran at 16mhz on a 33mhz intel 386 DX and seeing it almost keep up with the intel 387 at 33mhz and was very very impressed. What I didn't understand at the time was the first few Cyrix FPUs were limited to lower clocks, but when ran half bus clock they were able to avoid async latency penalties and their IPC was increased a measurable amount relative to clock (vs say running them at 20 or 25mhz on a 33mhz bus clock). So it made them look really really good. Of course running them at bus clock will be much faster but the ability to show it off at 16mhz was a great selling gimmick. Of course the Intel FPU would increase IPC in the same situation, but the salesman wouldn't ever bother divulging that. IIRC halving the clock of the FPU on a 33mhz bus would only slow it to about 60 or 65% and not to %50 like one would expect. Perhaps due to a relatively higher amount of memory bandwidth. This is why there was usually a minimal difference when I ran mine at 20mhz over 16 mhz in my computer at the time. Faster clocks were always better, but some dividers had less penalties than others. I saw no reason to run mine at 16 other than to impress people, but being a little bit OCD it just seemed more rounded. I am unable to recall however if the slower FPU would end up bottle necking the 386 at all due to it potentially tying up the system bus a little longer? I didn't think it an issue at the time. Some integer ops ran slightly slower after putting in the FPU (like maybe 3-5%) but from what I understand that was normal no matter what speed the FPU was. For what I was doing, it was a welcome boost and well worth every penny.
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Thank you. You put here some very valuable information and thoughts. Thank you, now I cant go to bed coz I need to test some things. 😂
@wishusknight3009
@wishusknight3009 3 жыл бұрын
@@CPUGalaxy lol good luck. I just got a very obscure joba few days back to extract some data from some really old QiC carts, and I happened to remember I had a special accelerator card for those floppy port based tape drives. I was up through the night trying to get it to work only to realize the drive I was provided was partly dead. Such is us retro enthusiasts. The spare they had worked perfectly though, and I was able to turn a 4 hour per tape extraction into about 30 minutes with the card I had. First time for me to ever use that card that I picked up on a whim cause I thought it would come in handy one day... That was 26 years ago. haha Thankyou for all the time you put in. It brings back memories and keeps my enthusiasm for playin around with my collections.
@roberthorwat6747
@roberthorwat6747 3 жыл бұрын
Wonderful stuff!!!
@gam85191
@gam85191 3 жыл бұрын
the cyrix really kicked ass
@djmccullough9233
@djmccullough9233 3 жыл бұрын
Cyrix Co-processors were pretty good. It was their CPU's that sucked.
@robgaros2985
@robgaros2985 3 жыл бұрын
@@djmccullough9233 Not quite. Their 386 CPU's were on par with intel's IPC and were clocked higher as well. At the time intel, despite being the designer, basically had the lesser chip compared to almost all competitors. It was their later socket 7 intergrated FPU units that were feeble compared to AMD, intel and IDT. Their integer units were actually quite a bit faster clock for clock as intel's at that time (hence the 200+ rating at 150MHz), but sadly for them Quake came along, which used the FPU.
@viniciusschneider705
@viniciusschneider705 3 жыл бұрын
I love vintage hardware! (And your channel)
@blackcorp0001
@blackcorp0001 2 ай бұрын
Awesome for screensaver demos ... amazing stuff
@patrickbateman3490
@patrickbateman3490 2 жыл бұрын
Very nice dude ! You make my day. Now I understand that the ULSI FPU is a good choice (I just ordered one) Thank you for your nice job :)
@jacq0272
@jacq0272 3 жыл бұрын
Nice comparison!
@Privatier-ce6oy
@Privatier-ce6oy 3 жыл бұрын
Great video with very nice comparison. I like this channel because there are very interesting informations.
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Thank you!
3 жыл бұрын
Love the video. I would also love to see these benchmarks run at the other CPU-s. If you can control for run-to-run variances, the fractal test could show even small differences, or maybe pinpoint some specific architectural traits.
@oliver1224
@oliver1224 17 күн бұрын
Very interesting video. I used to own the IIT DLC3 387 math chip in my old 66Mhz IBM Blue Lightning computer which I purchased back in late 1993.. First time I've seen that chip in years... quite nostalgic.
@DJ-Daz
@DJ-Daz 3 жыл бұрын
I messed around with POVRAY back in the DOS 5 days on a superb 486SX25. Renders would take hours to days to finish. When I upgraded to a DX2-50 it would take minutes to hours to render. I never did own a socketed co-pro.
@skagon_
@skagon_ 3 жыл бұрын
You really have to add the Weitek co-processors. They needed a different socket, but they were fast! I had done a similar (but more comprehensive) test about 18 years ago, comparing everything @ 20MHz, with what 387s I had available, but also with various 386 models. Apart from one graph (on some CPU forum which I cannot remember), I never published the results.
@MrMilli
@MrMilli 3 жыл бұрын
It's never too late to publish those results.
@Trancelistic
@Trancelistic 3 жыл бұрын
Another great video:)
@ronch550
@ronch550 11 ай бұрын
These old floating point chips make me appreciate the FPUs that come standard in today's modern CPUs, especially given how expensive these chips were back in the day. As a regular home PC user back then, these chips were nothing more than curiosities.
@solar3mpire
@solar3mpire 3 жыл бұрын
Our first 386SX mentioned a Weitek co-processor
@intrinia2832
@intrinia2832 3 жыл бұрын
As a child I came across different systems which had those empty sockets for Math CoProcessors and I always wondered what magic could be in there. Now I know for certain! Thanks so much, I love this channel!
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Thank you!
@intrinia2832
@intrinia2832 3 жыл бұрын
@@CPUGalaxy Keep up the good work and maybe follow up on the 287 or even earlier versions. ;-)
@wbushnaq
@wbushnaq 3 жыл бұрын
A great topic for those who don't know how we used to suffer back in the day! I appreciate this video and thank you so much for your hard work! Your brother, W.Bushnaq from Kingdom of Saudi Arabia
@eurocrusader1724
@eurocrusader1724 3 жыл бұрын
You have an impressive collection of hardware there! Respect. Edit , in 90-91' I was still running an Atari 1040 STe and an Amiga 500. The hardware you are showing was pretty high end/niche and indeed quite expensive at that time
@GeorgesChannel
@GeorgesChannel 3 жыл бұрын
Great video!
@i386dx
@i386dx 3 жыл бұрын
As an 386-enthousiast I can only like this kind of stuff. Very nice! Interesting and surprising results. I also have a selection of 387-FPU's in my collection; but I never bothered to actually test them like this. Just as you, I don't like empty sockets, so just installed one of them... I now learned that I did choose one of the slow one's ;-) (the ULSI MathCo).
@tomsun3159
@tomsun3159 3 жыл бұрын
if i remember correct, the Cyrix also has 4x4 Matrix functions build in, i don't know if any of the other brands has this feature, i think there were some libraries to bind while compiling.
@charonunderground8596
@charonunderground8596 3 жыл бұрын
Great test and comparison. I myself have in my 386DX 40mh, IIT 4C87 40Mhz coprocessor
@MattExzy
@MattExzy 3 жыл бұрын
"One of my personal favorite units."
@ereksat
@ereksat 3 жыл бұрын
Thanks for this!!!
@atheatos
@atheatos 3 жыл бұрын
Nice video as always :) I wanted to see this comparison. I was collecting 387s recently. I have 4 of them. The top models from Intel, ITT, ULSI, and Cyrix. Waiting for some 386 chips to test these. My 386 collection is very poor.
@scotthammond3230
@scotthammond3230 3 жыл бұрын
have my old Am386-40 with an IIT 387 running a manufacturing machine. Still running strong every day after all these years, even with the old "cheap" vga monitor.
@themax4677
@themax4677 3 жыл бұрын
I remember a long time ago (mid 90s) I stumbled across a free 287-10and man it made a huge difference with Links 286. Iirc it was actually 2MHz slower than the main cpu, but they seemed to get along well enough.
@5roundsrapid263
@5roundsrapid263 3 жыл бұрын
It probably was running at 12MHz. Only a 20% overclock, definitely possible.
@JeremyLevi
@JeremyLevi 3 жыл бұрын
@@5roundsrapid263 The 287 FPUs use a different internal clock modifier. If I remember correctly they run at 2/3rds the CPU clock, so his example was probably running underclocked at 8MHz when used with his 12MHz CPU.
@5roundsrapid263
@5roundsrapid263 3 жыл бұрын
@@JeremyLevi I wasn’t aware of that. Still, a massive improvement over a stock 286.
@JeremyLevi
@JeremyLevi 3 жыл бұрын
@@5roundsrapid263 I wasn't really aware of it either until I went looking for a 287 to pair with my Harris 286-16 and couldn't find anything faster than 12MHz FPU so I did some research. Turns out I only needed a 10MHz part. :)
@TheJeremyHolloway
@TheJeremyHolloway 3 жыл бұрын
Who made Links 286? I can only find references to Links 386 Pro...
@Zerbey
@Zerbey 3 жыл бұрын
Fascinating comparison, I remember there was a DOS utility that would emulate a coprocessor for CPUs that didn't have it, I wish I could remember the name of it as it actually gave a slight boost to performance. I recall wanting to buy a 387 back when I had a 486SLC and then being flabbergasted at the price - far outside of my range back then as a student!
@DevilsHandyman
@DevilsHandyman 3 жыл бұрын
I saw a familiar name in the list of FractInt contributors. Ken Shirriff.
@JosiahGould
@JosiahGould 3 жыл бұрын
Reverse engineering extraordinaire!
@wishusknight3009
@wishusknight3009 3 жыл бұрын
Master Ken.
@RachaelSA
@RachaelSA 3 жыл бұрын
This reminds of of when I started in IT, I remember so many of these things.
@shadowangel774
@shadowangel774 Жыл бұрын
The only thing I found so far is that the Cyrix FasMath CX-83D87-33-GP (and KN) models are asynchronous unlike others so they shut down unused parts of the FPU to save memory bandwidth on the data bus. Otherwise they were made same, same 32 bit bandwidth and data bus and same frequency. Will update as I find out more information.
@PCsrot
@PCsrot 3 жыл бұрын
Thank you for video, interesting
@HarikenRed1
@HarikenRed1 3 жыл бұрын
Was wondering if it makes sense to add a copro to my 486DLC40 CPU, as it is annoying to see an empty socket as you say... At the end, it's only an esthetics matter, without any purpose. Ahhh, the best part of the best DOS demo, Crystal Dreams II! You gave good tastes 😉 Schöne Grüße aus der Steiermark!
@FlopsPL
@FlopsPL Жыл бұрын
Even there is a demo, nice! I had couple years ago Cyrix FPUs, now only chips which I left are old 68040 cpus.
@savagemadman2054
@savagemadman2054 3 жыл бұрын
This comparison would have been fantastic for me in 1994. Our primary family PC at the time had a 100MHz IBM Blue-lightning CPU and a 33MHz Cyrix Fasmath. I had always felt the Fasmath let us down for performance, but now I know it wasn't actually so bad and just the low clock speed that was an issue. The computer was upgraded with an Intel DX2 Overdrive which was noticeably slower for integer but much faster for floating point, and then later with an IBM 5x86 that was much faster in every way.
@mFuSE81
@mFuSE81 3 жыл бұрын
If I remember correctly worms was a game that was unplayable slow on a 386-sx 20... But got a huge boost with a 387. Would be cool if you could test that :)
@LettersAndNumbers300
@LettersAndNumbers300 Жыл бұрын
And Falcon 3.0
@ryanmalin
@ryanmalin 3 жыл бұрын
This was a great video! I love fractals. I want to run some of these programs on my 10700k RTX2070 just to see how far along we've come.
@SauloMansur
@SauloMansur 3 жыл бұрын
I got a RTX2060 just for this purpose. The Optix API is amazing for playing with 3D raytraced fractals and procedural textures in realtime.
@zyzzyva303
@zyzzyva303 3 жыл бұрын
Fractint ftw! One of my faves when I was a kid.
@davej3781
@davej3781 3 жыл бұрын
My recollection is that the 486SX processor was a full 486DX processor with it's floating point unit artificially disabled. The 487SX "math co-processor" was in reality another fully functional 486DX CPU, with one extra pin to prevent it from being used in regular 486 boards, and also to prevent a regular 486DX from being used in a 486SX board. Once you installed the "487SX", it took over completely from the 486SX which simply sat idle in a halt state. The only upside to this whole ridiculous arrangement is that it later became possible to install more powerful "486" and "586" processors with clock-multipliers to get a genuine performance boost.
@vineilan
@vineilan 3 жыл бұрын
I found your channel to be very interesting
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Thank you very much!
@vincentpremel4817
@vincentpremel4817 3 жыл бұрын
Great benchmark ! It will be interesting to add the Rapidcad if possible !
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Rapid Cad I have already planned to cover it in a separate video. 😉. So for sure you will see it soon here.
@sebastienleger1174
@sebastienleger1174 3 жыл бұрын
This old stock looks fresh new with the quality of your prod! Glad I found you few months ago :)
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Thank you
@ATW2k
@ATW2k 3 жыл бұрын
I remember the Motorola 68881 math co-processor
@adamsfusion
@adamsfusion 3 жыл бұрын
Cyrix: Best FPU when it didn't matter, worst FPU when it totally mattered.
@jolilos
@jolilos 3 жыл бұрын
Twist: it was the same FPU just a few years later :)
3 жыл бұрын
If you think Quake mattered more than AutoCAD... They sure did something wrong looking at tit with 20/20 hindsight. But office people were always a good market. At Work we are trying to squeeze the most out of our equipment because, it is worth it. We keep an eye on how much time is lost due to waiting for machines to do their thing, and if there are time-saves to be had, it is usually easy to justify either effort, or hardware purchase so that people with quite high hourly wages do not sit idle waiting for their computers. Just calculate how much time (and money) is to be saved if 10 of your employees loose 5% of their time because slow machines, processes.
@robertbeighter6336
@robertbeighter6336 3 жыл бұрын
Would have loved to see a software emulator compared as well, man I spent some days in fractint. Great vid man, really enjoyed it.
@adriansdigitalbasement
@adriansdigitalbasement 3 жыл бұрын
I think software floating point is always used unless software is written to detect and take advantage of a hardware FPU, where it will use different instructions to do the calculations on the FPU... so there is no special Software emulated FPU -- as that is just what any program is doing already if there is no FPU.
@matthewday7565
@matthewday7565 3 жыл бұрын
There were 387 emulators that could trick a 387 demanding program to run (at vastly reduced performance)
@pete3897
@pete3897 3 жыл бұрын
@@adriansdigitalbasement Here here! :) The software emulation part is shown at 9:09 - he even says it :)
@HighTreason610
@HighTreason610 3 жыл бұрын
Very interesting and useful information. Expected the IIT to score a little better than it did, for no particular reason, though Cyrix was always king in the FPU department back then. It's a shame they couldn't keep up in later years. Going to have to re-test my own Cyrix 387DX, purely as I have to wonder if they were the same as the 83D87 versions or not, but don't have one of those (or the mysterious KN version). It should now be possible to deduce this from looking at your results, figuring out how far off my testbed system is with known chips (Intel, IIT) and applying that 'offset' to whatever the Cyrix chip scores. So thanks for doing these tests, very informative.
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
I thank you to see you here on my channel. ☺️. Just waiting hard to a new video on your cannel. actually you motivated me to make this 387 video. I recently watched a video from you where you got so mad of Landmark benchmark on your 386 setup. 😅. By the way, I love the intro you did for your videos now.
@francoisfritz198
@francoisfritz198 3 жыл бұрын
im re-watching the video and im late to receive my ULSI DX/DLC 40 Copro to push my 386DX 20 over its limits! thanks again for your amazing contend , take care F
@Kedvespatikus
@Kedvespatikus 3 жыл бұрын
Seeing that 487SX I'm officially envious now. :) That's a damn rare find! I'm waiting for that separate video about it. Edit: Fractint was a great program. For hi-res pictures with more complicated math it could took a night to render. I still have a lot of those fractal images on CD. And some of them printed in color and hanged on the wall. :)
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
soon. Just stay tuned on my channel. Thanks for watching! 👍🏻
@Kedvespatikus
@Kedvespatikus 3 жыл бұрын
2 nd edit: we populate those empty sockets, because they are there (freely after Sir Edmund Hillary)
@matthewday7565
@matthewday7565 3 жыл бұрын
The 487SX was a precursor to the ODP Overdrive (with the extra pin which turned off the existing 486 - oops, spoiler)
@kosmosyche
@kosmosyche 3 жыл бұрын
@@matthewday7565 I thought 80486 CPU's had an integrated FPU on them, I'm curious what was the purpose of a stand-alone additional FPU. Perhaps someone knowledgable could explain?
@kosmosyche
@kosmosyche 3 жыл бұрын
Nevermind. I just read about an i486SX (with FPU part disabled/removed) on Wikipedia, lol. Very cheeky of intel.
@JohnHeritage
@JohnHeritage 3 жыл бұрын
Very interesting fact on Simcity 2000 using the old FPUs!
@cringemaki
@cringemaki 3 жыл бұрын
I'm glad I found this channel. Love em processors. Also, I have a question: When this person was installing the co-processor, how did he manage to place it in the correct way? I didn't see any marks or guides.
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Thank you very much. Regarding your question I can recommend watching my video where I did a more detailed review on that board. And you are right, the right placing of the chip is an issue. here the link. kzfaq.info/get/bejne/p8d3hNuLqr_GqWQ.html
@cringemaki
@cringemaki 3 жыл бұрын
@@CPUGalaxy Yo, thank you. I'll investigate more and I'll watch that vid. Hope we get to see more of this content. Thanks.
@CaptainDangeax
@CaptainDangeax 3 жыл бұрын
It's amazing how Cyrix performed well with the KN and some years later failed in the same subject with Cyrix 6x86
@alreed2434
@alreed2434 3 жыл бұрын
MII correct?
@ChipGuy
@ChipGuy 3 жыл бұрын
I had one of those IIT FPUs. It could do 4x4 matrix multiplication. Good for graphics. Unfortunately it was not used by any commercial software I got.
@jjolleta
@jjolleta 6 ай бұрын
I remember the day I installed my 387 copro, aaah those good all days....... !!!!!
@hollyfarley7730
@hollyfarley7730 3 жыл бұрын
If I remember correctly, that i487SX is basically a full 486DX that checks that a 486SX is present, then disables it and takes over all processing by itself. Seemed like a bit of a scam, especially if your 486SX was just a DX with it's FPU disabled. Looking forward to the video on that one.
@johncate9541
@johncate9541 2 ай бұрын
You are correct. The i487 has a signal on one of the pins that disables the SX and takes over for it. I had a Dell 486 tower back in the 1990s that had a "487" socket. The good thing is that you could put any other 486 CPU in it and it would take over for the SX. So I installed a Kingston Turbochip with an AMD 5x86-133 that blew the doors off any silly i487SX.
@CoreyDeWalt
@CoreyDeWalt 3 жыл бұрын
I just bought a ulsi chip from china, and it was real! A perfect match for my ti486dlc. Pretty cool
@EricJorgensen
@EricJorgensen 3 жыл бұрын
I was messing around with some old computers a couple years ago and i discovered that some of the more recently compiled open source DOS tools were compiled in such a way that they require floating point. That was frustrating as one of the machines i was using was a passive backplane board with no accommodation for a 387 even if i had one. I recalled that back in the day there were fpu emulator TSRs for dos, and went looking, and found that you can still license them for a bunch of money. Oh well.
@jilmarit
@jilmarit 3 жыл бұрын
We had 8087 in XT-machine, then 387sx when moving to 386sx machine, after which the FPU was built in main CPU. My father used it for CAD-stuff, I merely for fractal rendering and Falcon 3.0. Funny how for me it was ”normal” to have FPU, but none of my friends had those. We then sometimes compared how long time it took to render some images, and with FPU it was a lot faster with proper software.
@RuruFIN
@RuruFIN 3 жыл бұрын
Interesting how they had identical scores, usually there's a little error marginal even when benchmarking many times with the same component :)
@GRAFHC
@GRAFHC 3 жыл бұрын
Excellent video! And of course now all the scalpers are going to start buying up Cyrix 33GP FPU's to resell on eBay for thousands lol ;)
@Limeayy
@Limeayy 3 жыл бұрын
i have a i9 9700k and i don't know what the big caps and 2 small caps or whatever on the bottom are called and don't know wher eto buy em. Can i fix a damaged pad?
@dabombinablemi6188
@dabombinablemi6188 3 жыл бұрын
Glad I've been holding off for months on deciding what FPU to buy. I really want my 386 (on one of those FOREX boards w/ clear jumper instructions on the PCB) to look proper...plus I'm trying to make it a bit faster than it was back when I last used it (around 2006-2007). Unless I find a 486 DX/2 66 cheaper.
@piecaruso97
@piecaruso97 Жыл бұрын
about games using the math co, there is the original quake and a game called retro city rampage 486, they both run on 386 hardware. Also a lot of software like some trackers makes use of it.
@SeanBZA
@SeanBZA 3 жыл бұрын
I remember using some shareware that emulated the 387 co processor in software, for the programs that absolutely needed the maths unit in there. While it was not as fast as the actual silicon, it came on on most testing as slightly faster than the actual CPU itself in doing this, more from optimised code for the functions than anything else, so would probably have cut the CPU only render times down to under 40 minutes.
@TheUglyGnome
@TheUglyGnome 3 жыл бұрын
I used the same with my 16MHz 386SX machine. Then while rendering AutoCAD 3D plots of my sister's house to be build, I got frustrated and bought a co-processor.
@4lpha0ne
@4lpha0ne 3 жыл бұрын
Yay, I had the ITT 3c87, for POVRay! (and demos + own coding ofc). It had a good price/performance ratio. I even called the c't magazine's hotline to help with my decision (I don't remember if Andreas Stiller was on the other end, but this is likely).
@pqrstzxerty1296
@pqrstzxerty1296 3 жыл бұрын
This example of FPU, is like also saying the comparison with Hypertheading when it arrived in CPUs.
@djmccullough9233
@djmccullough9233 3 жыл бұрын
no, no it isnt. Literally it isnt in any way like hyper-threading. Hyper-threading has no particular relevancy to Co processors. Hyper-threading is a modification to the cpu scheduler allowing each physical core to process instructions in a way that attempts to keep all parts of the CPU's actual processing pipline occupied. Think of it like an assembly line building parts, moving from station to station as each resource in the cpu is applied to each thread's needs. The effect is that Multiple threads can be processed 'at once' (between 2 to 4) to run on a single core while incurring as small performance hit as possible for 2 threads, and increaseing performance penalty for 3 and up.. An FPU in co-processor configuration would take over all computation of specific math instructions, largely bypassing the CPU all together.
@yoppindia
@yoppindia 3 жыл бұрын
Most interesting bit was the mother board which could fit 486 and 386 chips(I did not know it was possible), could you please repeat the same benchmark with 486 CPU?
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
yes, a follow up is definitely planned. several videos with that board. 😉
@georgewright1093
@georgewright1093 3 жыл бұрын
Thanks for telling me i don't need one of those, I was just about to order one to try and speed up my Ryzen system.
@ComputersAndRetro
@ComputersAndRetro 2 жыл бұрын
Cyirx? Excellent Video.
@AiOinc1
@AiOinc1 2 жыл бұрын
As far as I'm aware the 487 is just a 486DX that takes over all functions from the CPU. There are some early 386 boards which allowed you to use 287 coprocessors, it would be very interesting to see these in action and how they compare to the 387 setups! Would also love a follow up to see how much better the 40MHz parts perform at their rated speed with the AMD CPU. Makes me wonder what the top dog best setup is.
@Michael_Brock
@Michael_Brock 3 жыл бұрын
Good vid. Really great content from your channel. My only grumble would be out of the box thinking. Ie could you have stuck a 486dx 33 comparison at end. Ie the generation leap to 486 with integrated fpu. Edit typo
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
yeah, you’re right. would had been a great idea! 😓. Damn dude, why I did not have this idea 💡. But anyhow I have planned a video about the Intel Rapid Cad with that board. And there I will compare it then with the 486dx33. Thanks for your input. This is what I call a great audience and community.
@Michael_Brock
@Michael_Brock 3 жыл бұрын
@@CPUGalaxy hopefully with a back comparison ie a sub benchmark that has the 2 apps you used in this video with whatever apps you use for the rapid cad. Hopefully by Xmas you get the place you deserve in KZfaq half or 1 million subs, and growing.!❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Thank you very much buddy! and yes, I will use the same benchmark programs with the Rapid Cad to compare nicely.
@matthewday7565
@matthewday7565 3 жыл бұрын
Can the 40's beat the 33GP-KN if you pair them with the 40MHz - guessing there is no option to run the FPU at a different clock to the CPU
@fnordist
@fnordist 3 жыл бұрын
Do you have a 386 board with two FPU Sockets for Weitek and 387?
@-n3v-
@-n3v- 3 жыл бұрын
I'm curious about that motherboard you have used, would a 486 to Pentium Overdrive or equivalent chip work on that motherboard also? Yet another really interesting, detailed and well explained video. Great work. 👍🏻😃
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Thank you. Yeah, indeed this is a very interesting motherboard. But it does not support a Pentium OverDrive.
@AndreDeLimburger
@AndreDeLimburger 3 жыл бұрын
I am curious, are there any differences between them other then performance? Are there any known compatibility issues?
@esra_erimez
@esra_erimez 3 жыл бұрын
We take floating point arithmetic in hardware for granted. My dad used to write these things in assembly language. In the second volume of Knuth's book "The Art of Computer Programming" there is an entire chapter on multiplication "How Fast Can We Multiply?"
@dbracer
@dbracer 3 жыл бұрын
One thing of interest might be how well the various FPUs complied with the IEEE 754 standard. There were some interesting "bugs" in various cores, and also in the emulation libraries. (For some values of interesting, of course.)
@yvindaandalen6708
@yvindaandalen6708 3 жыл бұрын
My father worked with CAD and other structural engineering software. I always inherited his computers. Dual socket 4x86 dx2 and dual Pentium pro 200 were the most insane ones. I would really enjoy a review of those systems if at all possible, as they are lost to time. :(
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Dual 486DX?? Damn man, I have never seen one in my life. Would love to have that and make a review. Dual PPRO Board I have in my collection.
@yvindaandalen6708
@yvindaandalen6708 3 жыл бұрын
@@CPUGalaxy Neither of the machines are in my possession anymore. I can guarantee you that it was a dual 4x86 machine. I remember them as DX, but I would not die on a hill defending that. I had it for a few months before we traded it in for a Pentium machine (early 1995) as I was gaming, and NT was, well, not suited.
@simontay4851
@simontay4851 3 жыл бұрын
How do you know which way round the CPU/FPU goes in the socket. It can fit in the socket any way. If you get it wrong, the board and the CPU/FPU would be damaged.
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
good question. check out a video where I reviewed this board in detail. There I also explain the thing with the socket. kzfaq.info/get/bejne/p8d3hNuLqr_GqWQ.html
@johnps1670
@johnps1670 3 жыл бұрын
Nice video. Does a co-processor work faster/slower with different main processors (brand, clockspeed)? Will it change the ranking? How much faster is an integrated math processor compared to a seperate co-processor? To be continued?
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
good questions and definitely tbc. 😉. Integrated math copros started with the 486. so of course they were faster. on the 387 if we would increase the clockspeed to 40 MHz it will get also faster.
@Neksus-M06
@Neksus-M06 3 жыл бұрын
"But why are we collectors populating empty 387 sockets? Uh, you know the answer: yes, because we can and just hate to see empty cpu sockets." Made me laugh hard. But it's actually true. Even 287s if that matters. I have a few fpus and wanted to test them but decided not to because it would have taken time (sloppy excuse). After a few days I get this. Come on, coincidence in the galaxy? :)
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
😅👍🏻
@JorgeCarvalho_web_dev
@JorgeCarvalho_web_dev 3 жыл бұрын
Hi Sir, nice video! Can you please recommend an 387 for my 386DX40 build? It is only to populate the mobo. Do I need an xtal to go along? I have a xtal socket placed next to the 387 socket on the mobo. Many thanks!
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Mo extra xtal needed. just put a 387 into your socket. At the end it does not matter which one you take. even most of the 33 MHz versions run stable at 40 mhz. But usually the most available ones are the IIT @40 MHz.
@stephenvillagonzalo9967
@stephenvillagonzalo9967 3 жыл бұрын
Finally Cyrix won!! Wieitek was missing though
@CPUGalaxy
@CPUGalaxy 3 жыл бұрын
Weitek will be covered in another video. 😉
@pipschannel1222
@pipschannel1222 3 жыл бұрын
@@CPUGalaxy The Weiteks 3167s are pretty cool processors. Love to see more content on those! They're different beasts than the (Intel) x87 units and are way more flexible / versatile. They can be programmed independently as a memory mapped device, claiming a bit of system memory and run their own dedicated code, separate from the 386 CPU, something a 387 cannot do as it's directly bound to the CPU. Data transfers to and from the 387 coprocessor are accomplished directly through I/O lines and are automatically generated by the 80386 CPU for direct coprocessor instructions, being more of an 'addon' / extension for the 80386 CPU itself. The Weitek was more of a 'parallel' design in that regard as it could run its own custom developed calculation code and could output its results directly to a memory adress in RAM and did not need the main CPU to do that for it, freeing up valuable CPU cycles. Reminds me a bit of the Amiga's chipset that also did true parallel processing with a very advanced DMA controller for its time. IBM PCs were actually quite limited in that regard with their 'simple' little DMA controllers.. The Weitek units were mostly used for dedicated industrial purposes and certain customized scientific calculations where the 387 wouldn't cut it. For single precision floating point calculations the 387 was faster than the Weitek though. I wonder if there were people back in the day who were extreme enough to use both Weiteks and 387s at the same time. I think that's possible as my Compaq Deskpro 386 can take both a 387 and a Weitek and has 4 separate sockets (385, 386, 387 and Weitek), very cool stuff! 👍 Already got an IIT 387 in there, time to find me a Weitek 3167 and do some experiments 🤓
@opensparcbox
@opensparcbox 3 жыл бұрын
... together with Cyrix EMC87, maybe? :-)
@truckerallikatuk
@truckerallikatuk 3 жыл бұрын
Mate, why not find the original Intel tool from the overdrive kits? I have one, it's perfect for the job of removing chips.
20 MHz Intel 486SX Benchmark & Unboxing Overdrive CPU
20:38
CPU Galaxy
Рет қаралды 29 М.
1 or 2?🐄
00:12
Kan Andrey
Рет қаралды 47 МЛН
I CAN’T BELIEVE I LOST 😱
00:46
Topper Guild
Рет қаралды 101 МЛН
Nutella bro sis family Challenge 😋
00:31
Mr. Clabik
Рет қаралды 11 МЛН
MEGA BOXES ARE BACK!!!
08:53
Brawl Stars
Рет қаралды 36 МЛН
These VGA Cards have a COPROCESSOR!
29:23
PCRetroTech
Рет қаралды 17 М.
Faked Pentium CPUs / Huge Crime Story in 1996 + Giveaway
19:35
CPU Galaxy
Рет қаралды 61 М.
486DX4-100 MHz Benchmark Battle [ Intel, Cyrix, AMD, TI, ST]
12:54
IBM / Cyrix 6x86MX PR200 vs Intel Pentium 200 MMX
24:24
RetroSpector78
Рет қаралды 66 М.
Kahan on the 8087 and designing Intel's floating point
9:26
Turing Awardee Clips
Рет қаралды 3,9 М.
Arm vs x86 - Key Differences Explained
20:38
Gary Explains
Рет қаралды 386 М.
NEC V20 D70108D VS 8088 CPU Benchmark + Windows 1.01 Booting
15:59
These Keys Shouldn't Exist | Nostalgia Nerd
19:32
Nostalgia Nerd
Рет қаралды 647 М.
Игровой Комп с Авито за 4500р
1:00
ЖЕЛЕЗНЫЙ КОРОЛЬ
Рет қаралды 2 МЛН
Как правильно выключать звук на телефоне?
0:17
Люди.Идеи, общественная организация
Рет қаралды 58 М.
PART 52 || DIY Wireless Switch forElectronic Lights - Easy Guide!
1:01
HUBAB__OFFICIAL
Рет қаралды 33 МЛН