Less than 20 grand gets you a perfectly tuned 16 teraflop (single precision) "super computer".
Have you ever tried to make your application a debian package or RPM? It's a royal pain in the ass. Windows developers are not going to do whatever it takes to make this go smoothly on Windows.
There is a 100% chance that nearly every "Package-Install" command will just be downloading the app for you and launching the graphical installer you normally see.
People in charge of deploying software on windows are miserable people.
Nobody actually cares about the anti-trust case.
The general public doesn't like Microsoft because their Windows decides to reboot their computer for updates with no warning while they are working or giving a presentation.
The user experience for Microsoft products is generally pretty terrible.
The fact that windows does not have this in 2014 is shameful.
MOV EAX, [EBX]
What electrical components take 16 hours to boot up?
What mechanical operation requires 16 hours of prep?
Any insight? I read the article, and it had very little in the way of information.
Here at work it is my job to fix IT problems. When I see a server I see a box of problems. There is always something that can be "fixed."
A police officers job is to "catch bad guys." Whenever they see a person they see a "bad guy" they need to "catch."
Police are not your friends unless you help them "catch bad guys."
Just point a gun at his head and ask him "Convinced?"
This is the most concise explanation of a quantum computer I have ever read.
Then I remember he signed up for the circus.
Writing programs is pretty easy... relatively easy to the near impossible task of debugging programs.
I'm an artist that uses code to create my work (openFrameworks, processing, vvvv, quartzComp, libcinder, etc.). I code 15-18 hours a day. I am ALWAYS thinking about code.
My bugs bend my mind into a pretzel. I couldn't imagine someone who hardly cares about this putting in any real effort.
What kind of programs do people who do it only for a job write?
when rocks fall by gravity and break into pieces?
But Dell has given us so many memorable market defining products!
ALU * clock is meaningless measure. Hardware scales easily, code does not.
In HPC we call it "pleasantly parallel," nothing is embarrassing about it! =]
If your code:
-scales to OpenCL/CUDA easily.
-does not require high concurrent memory transfers
-is fault tolerant (ie a failed card doesn't hose a whole day/week of runs)
-can use single precision flops
Then you can use commodity hardware like the gtx series cards. I'd go with the gtx 560ti (GF114 gpu).
Make nodes with:
quad core processors (amd or intel)
whatever ram is needed (8GB minimum)
2 x gtx560ti (448) run in SLI (or the 560ti dual from EVGA)
Basically a scaled down Cray XK6 node. http://www.cray.com/Assets/PDF/products/xk/CrayXK6Brochure.pdf
It all depends on your code.