>Itanic
>>52018625
because it's almost 2016 and itanium is dead?
>>52018625
Because support was dropped like the plague.
Rlly want to use a xeon workstation rn senpai
>>52018661
>amd64 shills trying to sling their shitty kludge again
POO
IN
THEL O O
O O
O O L
>>52018673
if you need anything more out of your computer than the top-notch software offered on glorious HP(R)-UX(TM) you should probably reconsider your life choices senpai
>>52018804
But don't you want the Enterprise(TM) experience, senpai?
>>52018804
My workstation I use for work has a xeon and I'm a little dissapointed with the performance. Maybe I'm just biased because my personal desktop is a 4790k @ 4.7 ghz and this is only at 3.7.
This is so sad it isn't even funny
>>52018625
Because it got its shit completely wrecked by AMD_64
but I am
please kill me
>>52020859
It's eerie how similar the itanium sales forecast coincide with my life goals.
>>52022023
Post benchmark
>>52018625
what was wrong with itanium ? beside being incompatible with every software known to man kind
>>52022154
maybe next time I drag it out and can find a distro that runs properly on it, seemed to be pretty appreciable for the time last time I benched it with some basic shit like LINPACK
>>52022196
it simply didn't live up to market expectations, it was pretty nice when Intel and HP were demoing it in the late '90s, but a string of delays meant its competitors were ahead of it by the time it was finally released and the whole architecture was based around an advanced compiler that never really panned out the way they expected
literally the only thing keeping it alive right now are HP lawsuits and a couple chink manufacturers for some reason
>>52022196
It was that, and it was a colossal pain in the ass to code for. Add in that its x86 emulation was so poor as to be compared to a 100mhz Pentium and that AMD later made x86_64, and all the hype put into it was basically for naught.
>>52022275
HP is going to drop support for the latest Itanium series apparently.
>>52018625
was Itanium that bad, or AMD64 bandaid undeservingly killed it?
dead arch
dead chip
>>52022290
yeah, next-gen integrity and nonstops are going full x86
>>52022301
it was a cool idea that was just really, really disappointing in practice
merced's ia32 performance was appalling and slower than software emulation, the hardware was expensive as all fuck, the aforementioned shit ia32 performance meant that buying an ia64 system for consumer jobs was just butt fuck retarded since you could literally pull a system with equivalent performance out of the dumpster
>>52022392
pretty sad, i like exotic CPUs, remember IBM's 128bit CELL ?
Jesus that thing was brutal.
>>52022694
same, itanic is shit but the idea of it and the hipster cred makes me like it
makes me rather proud of my shitbox even though I never use it for much of anything but literal space heating
why arnt you using an intel pent 3? with w98 op?
oh lets not forget the nvidia gforce 200 series>>52018625
>>52023144
>shilling the 2MX unironically
You're even more of a meme than OP
>>52020191
Xeon is the definition of enterprise.
>>52023144
Because I have a based p4 fgt
>>52023144
>Pentium III
>not an overclocked Pentium 4 paired with a NVIDIA® FX 5800™ Ultra ayy housefire reverse-cooled edition®™
>>52022023
What was so bad about itanium? is it another dank meme or did jewtel fuck it up?
>>52026073
part meme, part reality, tried to explain it in >>52022275 and >>52022392
>>52026073
it was one of the competing 64bit instruction sets that were fighting to be the new standard.
But AMD actually won out by creating AMD64, commonly known as x86_64. It was an extension to the existing 32bit x86 instruction set.
>>52026127
Man it sucks if AMD goes under due to Nvidia and Intel. These guys were innovators back in the day.
I am yearning for a nice 16:10 AMD APU based laptop but no manufacturer is stepping up. Every model is inferior specs with 1366x768.
>>52026127
semi-true, but IA64 was in the works long before anyone was even thinking of adding 64-bit extensions to IA32, you can probably argue that AMD64 exists because of the former's failure to succeed the latter in the mainstream, instead it was doomed to live the rest of its days as a crude vendor-locking tool for HP in mission-critical systems and big database servers
why is that logo so SHIT
>ugly lighting effects
>"intel inside" is small and high up
>word ITANIUM has awful kerning, is stuck on left side of logo
>bad fonts all around
>>52022196
Too much expectation on compilers to be able to ahead-of-time optimise programming flow for the slots. The assembly language was pretty vile. VLIW can work on a GPU, but even those are fading away to smaller designs: on a CPU, where branch misprediction is a thing, it was a mistake.
It does have a few nice ideas, some of which were borrowed by RISC-V, and that's where EFI came from (now UEFI): I'm not sure I'd have chosen that over OpenFirmware's FORTH bootstrap, necessarily.
The NSA were large sponsors for their own uses, and are the last large-scale users of ia64 I know of, but even for that usage, GPUs beat it, so they're buying Teslas now to replace them and running x86-64 boxes with RHEL and Debian.
>>52027912
Early 2000s design was utter cancer
>>52028033
I'm surprised they've kept it up that long, everything since Tukwila just looks like a limp dick even considering Itanium's supposedly god-tier FPU performance
