Good Q&A on Jini

An interview with Jim Waldo
An old one, but answers a number of questions that people continue to ask even now.

btw, he blogs here

The first Dual core Opteron servers are out.

Sun announces V40z's with dual core opterons. Sets performance records with the new irons.

netBeans build

Just built netBeans from the sources on my machine. :-)
Check these links for more info...

http://www.netbeans.org/kb/articles/buildAndRun.html#adding_modules
http://www.netbeans.org/kb/articles/start_dev_NB.html

DTracing Java

If you're a java developer & you haven't read this entry of Bryan Cantrill's blog, you really have missed something.
One word - IT ROCKS!!!
Such level of profiling & so many intricate details of the method calls, all in a very comprehensible manner is, like the blog says, without precedent.

Yet another tp survey

A survey that tries to guess "What kind of a movie you belong to"...

I belong to....
Pirates of the Caribbean!

What movie Do you Belong in?(many different outcomes!)
brought to you by Quizilla

Took a toefl-like quiz that measures the extent to which one's english is americanized (read polluted). I didn't do very badly, actually, considering my exposure to american claptrap - ;-)

English Genius You scored 92% Beginner, 100% Intermediate, 100% Advanced, and 93% Expert!

You did so extremely well, even I can't find a word to describe your excellence! You have the uncommon intelligence necessary to understand things that most people don't. You have an extensive vocabulary, and you're not afraid to use it properly! Way to go!

My test tracked 4 variables How you compared to other people your age and gender: You scored higher than 37% on Beginner You scored higher than 72% on Intermediate You scored higher than 88% on Advanced You scored higher than 98% on Expert

The Commonly Confused Words Test on Ok Cupid

Why slashdot plays home to the anti sun flame-throwers

This is the first plausible reason you'll find when you try figuring out why the slashdot editors so readily approve anti-sun posts - like this anonymous comment at Grisanzio's(opensolaris community manager) blog suggests -
"I think Slashdot has been specifically targetting Sun, lately, probably because their behind-the-scenes financial interests revolve around Linux." Isn't that obvious?

Excerpts from Tom Ball's Blog: Exceptional Debugging

A rather clever way of checking whether a class exists in the current class path:

public boolean classExists(String name) {
String resource = name.replace('.','/') + ".class";
return getClass().getClassLoader().getResource(resource) != null;
}
This was suggested by a java.net use "brucechapman" in response to Tom Ball's latest blog entry - Exceptional Debugging

Solaris Sys admin guide collection

Useful link if you want to tune a few parameters for your app (not that i do.. :-) )
Sys admin guide collection
Here's a good collection of Zone demos.

Why Eclipse users are moving to NetBeans

Good read...http://cld.blog-city.com/read/1126337.htm
No surprises there. Eclipse's SWT sucks on Linux while NetBeans behaves like the angel that it is even on Windows. Why? NetBeans' UI It's pure java. No native code at the Window Manager Level. It doesn't try to make native calls for showing every small widget (like SWT does). SWT, that wy, is an antithesis to the java philosophy (where you have all the native code only at the VM level and avoid, to the extent, possible, native calls at your app level to keep your code truly class platform). Naive windows users fall for the "oh so windows-like" look and feel on exlipse on Windoze. Try it on Linux or Mac and you'll know the difference (in speed & LAF) between Eclipse and NetBeans. Eclipse looks broken & frayed on all other platforms except Windows. And if like Eclipse's "native" LaF so much, i'm afraid, you're tending towards an C++ based Java IDE like MS J++ (and you have not right to call yourself a true blue Java dude).

Vintage Jonathan!

Jonathan is simply awesome in his latest blog.

I'm quoting the entire entry here, just for the reader's benefit...

Quoted blog Begins:

The Economies of Scale - The Scale in Economy

One of my best friends in life started his professional career at Carnegie Mellon University, where for a while he worked (back in the 80's) on the challenges surrounding parallel computing. Back then, it was a relatively esoteric field, in which one of the challenges was finding problems that lent themselves to parallel approaches, and another was trying to build programming models that made those problems tractable.

Spooling forward about 20 years (yipes), during the recent Boston Red Sox victory, MLB.com served 100,000,000 page views to 10,000,000 unique visitors. Each doing roughly the same thing. Talk about massive parallelism, it's in front of our eyes. The internet itself has yielded the world's largest parallel applications - from instant messaging, to bidding on beanie babies.

Now Sun has long been an investor in parallelism. First, we built systems capable of managing tremendous load (we're honored to supply the infrastructure under America's baseball addiction); and as importantly, we built an operating system that knew how to manage multiple threads of execution. Managing parallel "threads," historically one per CPU, is key to scalability - simply put, the more work you've got to do, the more CPU's you throw at the problem. And having an operating system that knows how to run efficiently across 100's of cpu's is a handy thing, at the core of Solaris's reputation for "scalability." Standing on the shoulders of giants, the Java platform was built with parallelism in mind, too.

Now oddly enough, despite the crises introduced when businesses have insufficient capacity, more often, businesses have too much capacity - average utilization in a datacenter is something like 15%. Which means most businesses waste enormous sums of the money on systems (not to mention the concomitant waste in power to keep dormant systems on, cooled and housed). Mainframes, historically, had very high utilization. Why? They were (and are) incredibly expensive, but they also have a feature called "logical partitioning" (LPARs) which allows big systems to be divided into many smaller mainframes. Until this year, no non-mainframe operating system offered logical partitioning. (Paraphrasing Gilder, "you waste what's cheap." Jonathan's corollary, "Until you build your whole datacenter out of it.") That is, until a few weeks ago.

One of the key features in Solaris 10 is just this - "containers" are logical partitions that allow a single computer to behave like an unlimited number of smaller systems, with little/no overhead. Reboot a partition in 3 seconds, keep disparate system stacks on the same computer, assign different IP addresses or passwords to each, treat them like different computers, and use them to consolidate all those otherwise 15% utilized machines - sky's the limit (on any qualified hardware platform), and with it, customers can now drive utilization through the roof. With no new licensing charges. (And personally, I'm a fan of 3 second reboots.)

But back to baseball. One thing to recognize with businesses like MLB.com (and Google and Amazon and eBay) is that system level performance is now all about parallelism - defined as the art of behaving well when 3,000,000 baseball viewers (or searchers or shoppers or bidders) arrive to use your service. Sun, in fact, saw two years ago what Intel saw this year, that the gigahertz race was over. So we biased our entire system roadmap to "thread level paralellism," and started designing systems with many, rather than one, thread per CPU. Most SPARC systems now ship with two threads of execution per socket (standard in all UltraSPARC IV systems). But that's just a baby step toward true parallelism.

How parallel can we get? Niagara chips, built into our upcoming Ontario systems, will feature 8 cores, each with 4 parallel threads of execution - 8 times 4 yields a 32 way system - on a single chip. These systems will consume far less electricity and space than traditional system designs - and will be optimized for MLB.com style applications: thread sensitive, big data, throughput oriented apps. Moreover, they'll drop our customers' power bills and real estate costs - which may not sound like the class of problem today's CIO cares about... until you actually talk to a CIO. Massive power and space bills are a big problem, and the physics of cooling a space heater is a more popular topic than you'd think. (btw, a dirty little secret - remember California's power crisis a few year's back? One of the leading suspects? Computers chewing up huge amounts of power, and producing heat, which required air conditioners, which chewed up even more power...)

As we scale out these systems, it's perfectly reasonable to expect greater and greater levels of parallelism. And the good news is not only do Solaris and Java (and most of the Java Enterprise System) eat threads for lunch, but with logical partitioning, we can deploy multiple workloads on the same chip, driving massive improvements in productivity (of capital, power, real estate and system operators).

But let's not stop there. Simultaneously, much the same inefficiencies described above have been plaguing the storage world. A few years back, "SSP's," or storage service providers, began aggregating storage requirements across very large customer sets, providing storage as a service. Most SSP's found themselves stymied by the diversity of customer they were serving. Each customer, or application opportunity, posed differing performance requirements (speed vs. replication/redundancy vs. density, eg). This blew their utilization metrics. Before the advent of virtualization, SSP's had to configure one storage system per customer. And that's one of the reasons they failed - low utilization drove high fixed costs.

So that was the primary motivation behind the introduction of containers into our storage systems. The single biggest innovation in our 6920's is their ability to be divvied up into a herd of logical micro-systems, allowing many customers or application requirements to be aggregated onto one box, with each container presenting its own optimized settings/configurations. This drives consolidation and utilization - and when linked to Solaris, allows for each Solaris container to leverage a dedicated storage container. Again, driving not simply scale, but economy.

On top of all this, the same challenge has plagued the network world - diverse security requirements, and a desire to partition networks into functional or application domains, have driven a proliferation of "subnets" for applications, or departments. HR, Finance, Operations and Legal, for example, each require their own VLANs (virtual local area networks), the result of which is a gradual increase in partitioning, paired with a creeping inefficiency in network utilization - as the static allocation of subnets outpace anyone's ability to manage them. (If you recall, prior to their downfall, Enron - one of the beneficiaries of California's power crisis - was setting out to create a market for surplus network capacity - nice idea, turned out to be tough to execute).

This was the primary motivation behind Sun's building containers in to our application switches - the devices that now sit in front of computing and storage racks, to help optimize performance of basic functions (network partitioning, security acceleration and load balancing, for example). The network itself can be divided into individual network containers, or virtual subnets, and programatically reprovisioned as loads change.

Meaning that a customer can now divide any Sun system into logical partitions or containers, each of which draws on or links with a logically partitioned slice of computing, storage and networking capacity. Which presents the market with an incredible opportunity to drive utilization up, and exit being one of the most inefficient (and environmentally wasteful - where are the protests?).

Which is a long way of saying the internet is the ultimate parallel computing application - millions, and billions, of people doing roughly the same thing, creating a massive opportunity for companies that solve the problems not only with scale, but with economy. A unit of computing has been detached from a CPU, to whatever a baseball fan wants at MLB.com. Or a bidder wants at eBay. Or a buyer at Amazon. Can you imagine how big a datacenter MLB.com would have to build if we were still in a mode of thinking each customer got their own CPU?

Just think about that power bill.

_________________

Some other thoughts:

What happens to software licensing in a virtualized world? What's a CPU in a per-CPU license when the system you're running has 32 independent threads? An anachronism in my book. Can you imagine if MLB.com charged by the CPU? That's why all software from Sun, from the OS to the middleware, will be priced by the "socket" or employee. We believe the rest of the industry should move in the same direction.

Who's the ultimate beneficiary of this mass virtualization? In the short run, customers who can now both recover dormant capacity and boost productivity (consolidate to Solaris 10, UltraSPARC IV, our 6920's or our app switches - have yourself a "look at all this capital I freed up!" experience, and guarantee yourself a spot at your CFO's summer party).

But the ultimate beneficiary may be the company that deploys all these systems - and can link together, as well as dynamically provision across, it in its entirety. The combinatorics are staggering - thousands of containers, against thousands of threads against the same orders of magnitude in storage and network partitions. That's some serious scale. Requiring some serious economy in provisioning and operation.

So what business could possibly require or operate infrastructure at that scale? Sun's Grid, of course. No reason to think we won't be serving one of the largest markets in the world - driving utilization to be both prudent, and responsible.

(End of quoted Blog)

This man has SOME talent, doesn't he? How can you not be his fan???

S10 installtion walkthrough

There's a nice walkthrough (with screenshots) of S10 installation here. Really cool.
btw, i installed S10 on friday on a test machine at office. Absolute bliss. That's the phrase. More on that later...

Arrogance is still the #1 characteristic of IBM

Author/Freelancer Dave Taylor writes:


But then Gerstner comes across as remarkably arrogant and elitist as he shares the "tedious obligation" of having to go to formal fundraising events for major charities, the experience of having a fancy multi-story apartment in a chic area of New York City and a second house on the beach in Florida. Yet when he joins IBM, Gerstner complains about the stodginess of the executive team but has no compunction flying around on the IBM corporate jet or having his "driver" show up in the morning to chauffeur him to the office.

I realize that when you're the boss of a multi-billion-dollar corporation, there are certain perquisites that not only go with the job, but are expected, but it seems awful disingenuous to talk about cutting costs, rethinking executive reporting structures, and maximizing the cash reserve of a company when you can't hop on a commercial flight or drive yourself to work...

On the plus side, the book is compelling, interesting listening so far, and Gerstner shows that he had a keen eye for corporate dysfunction and that IBM really was a company on the rocks, stifled and drowning in a frozen bureaucracy rife with "lifers". His description of how senior management meetings were nothing so much as the IBM version of multinational diplomatic negotiations is quite fascinating, for example.

Hmm.. any surprises there? The dinosaur is still the most arrogant animal in the forest (if only prehistoric & irrelevant).

The Solaris album of white papers.

An excellent compilation of articles on Solaris' implementation of various OS sub systems.


Published by Sun's Ozan yigit> :

Shared Libraries in SunOS

Virtual Memory Architecture in SunOS

SunOS Virtual Memory Implementation

Realtime Scheduling in SunOS 5.0

SunOS Multi-thread Architecture

Beyond Multiprocessing: Multithreading the SunOS Kernel

Implementing Lightweight Threads
Symmetric Multiprocessing in Solaris 2.0 [link not found]
Proceedings of the thirty-seventh international conference on COMPCON,
San Francisco, California, 1992

Vnodes: An Architecture for Multiple File System Types in Sun
UNIX

Evolving the Vnode Interface

Efficient User-Level File Cache Management on the Sun Vnode Interface

Extent-like Performance from a UNIX File System


Design and Implementation of the Sun Network Filesystem

The Sun Network Filesystem: Design, Implementation and Experience

Virtual Swap Space in SunOS

Profiling and Tracing Dynamic Library Usage Via Interposition

tmpfs: A Virtual Memory File System
The Translucent File Service [link not found]

The Automounter
The Automounter: Solaris 2.0 and Beyond [link not found]

The Autofs Automounter

Enhancements to the Autofs Automounter
Removable Media in Solaris,
Proceedings of the Winter 1993 USENIX
Technical Conference, San Diego, California,
USA , January 1993.
USENIX Association.

Zero-copy TCP In Solaris
The Process File System and Process Model
in UNIX System V
[link not found]
Evolution of the SunOS Programming Environment,
Proceedings of the Spring 1988 EUUG Conference,
Cascais, Portugal, 1988.


Implementing Berkeley Sockets in System V Release 4

Secure Networking in the Sun Environment

Fast Consistency Checking for the Solaris File System

System Isolation and Network Fast Fail Capability in Solaris

CPU Time Measurement Errors

Solaris Zones: Operating System Support for Server Consolidation

Solaris Zones: Operating System Support for Consolidating Commercial Workloads

The Slab Allocator: An Object-Caching Kernel Memory Allocator

Magazines and Vmem: Extending the Slab Allocator to Many CPUs
and Arbitrary Resources

Automatic Performance Tuning in the Zettabyte File System

Existential QoS for Storage

Dynamic Instrumentation of Production Systems

FireEngine - A New Networking Architecture for the Solaris Operating System

Some of these papers are like chapters from a book on modern OS concepts. Brilliant.

S10 beats Linux on network performance

A comparison between the network performance of Linux(RHEL) and S10. Evidently, S10 beats Linux, except in the low end single cpu(32 bit) category, by a good margin. Cheerio!!

Oscillating between literature and music

This came as a bit of a surprise to me, but the blogthing questionnaire says:

Your Dominant Intelligence is Musical Intelligence

Every part of your life has a beat, and you're often tapping your fingers or toes. You enjoy sounds of all types, but you also find sound can distract you at the wrong time. You are probably a gifted musician of some sort - even if you haven't realized it. Also a music lover, you tend to appreciate artists of all kinds. You would make a great musician, disc jockey, singer, or composer.

What Kind of Intelligence Do You Have?

I was totally taken aback; shocked, in fact. But, guess what, I went back to the questionnnaire and changed just one answer to indicate that i enjoyed writing more than i did singing a solo, and this is what turned up -

Your Dominant Intelligence is Linguistic Intelligence

You are excellent with words and language. You explain yourself well. An elegant speaker, you can converse well with anyone on the fly. You are also good at remembering information and convicing someone of your point of view. A master of creative phrasing and unique words, you enjoy expanding your vocabulary. You would make a fantastic poet, journalist, writer, teacher, lawyer, politician, or translator.

Thank you, thank you. Now,that's a relief.Whewww!!

Sun #1 Unix seller in 2004

This article quoted the yearly gertner report that just came out, stating:
"Sun retained the top Unix sales position, with $5.14 billion in sales, compared to HP's $4.89 billion and IBM's $4.32 billion. If IBM's current 7 percent Unix growth rate for 2004 holds and HP's and Sun's Unix sales continue to shrink by their respective 7.8 percent and 5.3 percent, Sun will still be the number one Unix vendor in 2005, but HP will drop to number three behind IBM."

And the report corresponds to a time when Sun hadn't even unleashed the power of Solaris10. Hopefully, things can only get better hereon. What will HP & IBM do? Run for cover and take refuge under Linux and Windows to escape the wrath of Solaris.The battle has only just begun (with Sun changing the rules of the game, again) :-)

A parody on HP

This site is the most hilarious spoof i've read/watched. Especially these pages -

1) Corporate news
2)New CEO candidates
3) Brand strategy
4) Offices of the future

Simply brilliant. What else can I say?!!

Some real good quotes from fortune

1)Q: How many Micro$oft programmers does it take to screw in a light bulb?
A: 472. One to write WinGetLightBulbHandle. One to write
WinQueryStatusLightBulb. One to write WinGetLightSwitch-Handle...

2)On the Internet, nobody knows you're a dog.
-- Cartoon caption

3)It may be bad manners to talk with your mouth full, but it isn't too
good either if you speak when your head is empty.

4)
"I made the decision to name the Justice Department building after Robert
Kennedy because he's deservant."

George W. Bush
November 20, 2001
Speaking to reporters in the Oval Office about his decision to name the
Justice Dept. building after former U.S. Attorney General, Robert Kennedy.
Aired on CNN.
(NOTE: I'll be updating this particular entry with new quotes as & when i find them.)

James Gosling on SWT

Some good points by Gosling on why SWT is a fast, light weight way to (porting) hell...

"The SWT thing was just…it pissed me off beyond words. So, if you wind back the clock a few years, the original toolkit in Java was this thing called AWT, the Abstract Window Toolkit. It’s still there, and it’s a fairly simple, straightforward toolkit, and it’s based on using the widgets from the underlying (inaudible). It had a wide variety of really, really ugly problems, things like how to get semantics consistent from platform to platform, and some of the little fringe things like cut and paste. Trying to get cut and paste to operate correctly between text widgets, like between the Mac text widgets, the Motif text widgets and the Windows text widgets. When you’re actually trying to use those text widgets in their native homes, it’s just a nightmare. How do you deal with things like subcopying, how do you make a button extensible? How do you deal with the more advanced features that people want, like being able to do tables where you can control the rendering of components and cells and that kind of stuff?

A lot of those things were completely precluded by the AWT architecture. IBM in particular was really upset about the way that the AWT architecture had gone, and they were one of the leading agitators that caused Flame to be created. In fact, about half of the engineers on the Flame team were actually from IBM -- they actually got IBM pay cheques. IBM built Apple Flame, and actually then Swing was quite successful, it’s been successful for quite a while. The biggest problem with Swing was that it can do so much that it’s kind of become like the 747 cockpit if you like APIs. There’s a lot of complexity there, and the hard part is figuring out how to use it. It’s in this weird situation where pretty much anything you can want to do in Swing, you can do easily. But what’s hard is to figure out the easy path through all of the different options, the different ways you can do things. Once you figure out the one true path to get what you want done, then it’s pretty easy. People often say “Why don’t you just make it easier by simplifying it?”, and say, “so you simplify it in this way, it would make my life better”. But then for the next guy it would be worse, because he wants to not go there, he wants to go on this particular path. So it’s been difficult to manage the complexity right.

So, wind the clock forward a few years, and there’s (inaudible) from IBM (inaudible) “Swing is too complicated, let’s do AWT all over again”, and if you look at the SWT architecture, it’s almost exactly the same as AWT. It has all the AWT problems: it’s way simple, it doesn’t port very well. And its API is somewhat different, because essentially what they did was they made the Windows version really easy by making their API pretty much a clone of the Windows API. And then on Linux, they tried to make Motif look like the Windows toolkit. They’ve got those mapping layers that are just like, really horrible, and it only kind of works. And same thing in OS X, their porting problems from platform to platform is a nightmare, their consistency (inaudible) is a nightmare. And it’s sort of like, “You were there seven or eight years ago. It was a bad place to be, don’t go back!”. The problem is that IBM is like three hundred and some-odd thousand people, so there’s like a cluster of people. Most of the people we were working with back then were in North Carolina and New York State, like Westchester, and they actually understood things pretty well."
Original Q& A transcript - James Gosling Q & A