Oracle To Invest In Sun Hardware, Cut Sun Staff
An anonymous reader writes "There's been much speculation as to what Oracle plans to do with Sun once the all-but-certain acquisition is complete. According to separate reports on InfoWorld, Oracle has disclosed plans to continue investing in Sun's multithreaded UltraSparc T family of processors, which are used in its Niagara servers, and the M series server family, based on the Sparc64 processors developed by Fujitsu. However, Larry Ellison has reportedly said that once the Sun acquisition is complete, Oracle will hire 2,000 new employees — more people than it expects to cut from the Sun workforce. Oracle will present its plans for Sun to the public Wednesday."
However, Larry Ellison has reportedly said that once the Sun acquisition is complete, Oracle will hire 2,000 new employees — more people than it expects to cut from the Sun workforce.
This is not right from the article. Oracle plans on hiring 2000 employees, but they plan on reducing Sun's headcount by more than that. Hope those Sun employees pick up jobs quick in this rough economy...
From FTA:
Ellison told The Wall Street Journal that Oracle plans to take on 2,000 new employees - but that it will reduce Sun's head count by a larger number.
I wonder what the motivation here is. Oracle isn't exactly known as a warm and fuzzy employer. Every time I've had to deal with Oracle products, it's painfully obvious that the people they have intentionally design their software to be difficult to support...and then they hire armies of low-skill consultants to "help" customers install their systems.
(And yes, I understand enterprise-grade software is complex. However, needing someone to guide you through all the quirks in the products or documentation just to get a proof of concept going is sad. I think SAP may be the only worse company in this "doesn't work out of the box" category.)
My guess? Larry is going to wipe out the current long-tenure Sun employees who know everything about Sun's products and replace them with low-skilled, low-salaried n00bs. My further guess would be that these employees would be in lower-wage countries as well.
IBM has been doing stuff like this for a while, from what I've heard...including offering people permanent one-way transfers to India along with the appropriate salary cut. Every time one of these crazy schemes comes to light, I really wonder what I should do with the rest of my career...I have at least 30 years until I retire!!
I can't believe what's happening, first ax the moon, now cut the sun, not to mention this thing about mars' spirit being stuck. What the hell is going on with our solar system ?
IANWYTIA (I Am Not Who You Think I Am)
As an Oracle employee, I can tell you "fear-based fealty" is not at all how Oracle works. They have a long history of acquisitions, and the strategy is always the same: Keep the best and brightest from the acquired company, and let everyone else go. Heck, they've bought entire companies before specifically so they could get their best engineers (virtual iron). They're practically obsessed with getting the best people, not the best bootlickers.
All of it was mentioned, with the exception of the C, C++, and Fortran compilers.
Maybe someone else can fill in more details.
Breakfast served all day!
The most interesting thing about that was that the 'auto parallelization' code used 8 cores to get slightly more than 50% more performance than it got with one core. To be honest, I'm a bit surprised that it got any benefit. It's parallelizing loops which can only be done if the compiler can prove that there are no dependencies between loops (which means that it must be able to see all of the code that executes in the loop, including the bodies of called functions) and it will often result in slowdown because subsequent loop iterations will use data in the same cache line, so you get a lot of churn.
Compiler performance is very important on the newer UltraSPARCs, like the T1 and T2, because they do not do out-of-order execution. That means that data dependencies between instructions can cause pipeline stalls (which, hopefully, won't be a problem because you've got another thread or seven waiting to run). The compiler needs to know the length of the pipeline and design the instruction stream with this in mind. It also needs to do things like space floating point operations for the T1, which has a much larger floating point latency than most other chips. Moving data between the floating point unit and an integer register (e.g. branch on a comparison between floating point values) takes several cycles, so it needs to be aware of this and shuffle the instructions accordingly.
I am TheRaven on Soylent News