SunFireT2000After being tipped of on the Sun try-and-buy program by Alan Baker, a coworker and cohort, I figured I’d throw my hat into the ring for a chance to test drive a SunFire T2000… and today it arrived.

Here’s what Sun has to say about their program:

Toss your toughest workloads at the multithreaded Sun Fire T2000 server with the Solaris 10 Operating System, and watch it crank up your database and Web application performance.

We’re so confident in the quality and performance of the world’s first eco-responsible server, we’re offering a free 60-day trial, risk-free. If you’re not totally impressed, just send it back at our expense and owe us nothing.

Chances are that you will be dazzled by your trial server and come back for more. The new Sun Fire T2000 server will likely become your multithreaded workload energy-saving powerhouse of choice.

When you apply for the Try and Buy program you get the choice of a four, six, or eight core 1GHz UltraSPARC T1 processor. I chose the eight, not just because bigger is better, but also because it is closest to our production Oracle servers in capacity and price.

So once we can find the time we’ll get 64-bit Oracle installed on there and run it through the paces. On deck are some join, function, lookup intensive datamart creation scripts which currently crush our production server every evening. This should be fun.

Also of interest is Sun’s claim of this server being “the world’s first eco-responsible server”. While I am unlikely to bring in a kilowatt meter to verify these claims, we are a very green university and hey, everyone wants to save a few bucks on electric.

UPDATE: I have now had the chance to test drive some Oracle jobs on this system. Check out my findings here.

oracle, database, database administration, database administrator, dba, dbms, rdbms, sun, solaris, systems administration, system administration, sysadmin, unix, t2000, try and buy, sunfire

Update: The winner has been anounced. Click here to find out who won!

As I sit here watching the debut of ABCs American Inventor I am completely underwhelmed. The best of these showings are a weak mashup of existing products. E.g. the solar powered cooler. Whoopee. Other inventions do have a limited market, but I see very little here which will change how people live.

The highlight of the program is the fashions of Doug Hall, the only actual inventor on the judge’s panel. He also seems like the only one with any interest in the actual inventions. While the other judges are investors and executives, Doug is the complete package. He has made a career out of inventing not in a limited market space, but working with corporations to advance their innovation. He is an active lecturer and a published author.

Most inspiring is a 14 year old boy who has come up with an air-conditioner for the car window so you can leave your dog in the car on a hot day. He didn’t make it, but his resolution to work harder and come back with more means to me we will hear more from him in the future. He is the American Inventor. Despite rejection he received some great advice from Doug. I failed to catch his name but I do hope he continues on.

From what I’ve gathered about the show, twelve inventors will be given $50,000 each to advance their invention. America will choose a winner (although I’m not exactly sure how, probably phone voting) and that winner will receive one million dollars. A heafty sum, but why should a single invention be the measure of the next great American inventor? The show is “American Inventor”, not “American Invention”. A great inventor should be able to broaden their scope to address new challenges, new needs, and new market spaces.

What if these inventors were forced to compete in different areas? Household items, transportation, electronics, office technology, entertainment, the list could go on. At this point I’m truly afraid that the nut bowl with hidden shell discard and the branch cutter (which seems to be just a branch cutter, yes, both of these moved on to round 2) may just win this competition. I hate to say it but the edible snow globe was the most innovative invention I saw tonight. Hell, it’s better than those stupid chocolate fountains that doned the shelves of every retailer this past holiday season.

So I’ll tune in to American Inventor again, but I’m really hoping for more. In the meantime I’ll stick to Make Magazine and the Makezine Blog for my invention fix.

american inventor, inventor, invention, innovation, reality television, reality tv, television, tv, entertainment, inventing

Web surfing today I stumbled upon Ora-WTF.blogspot.com. This will be one to follow.

Now most of the world won’t understand why logging users clear-text passwords in a table is a bad idea, or that your error handling should handle errors, not cause them, but for those of us who get some perverse pleasure from disaster prone, elaborate solutions to everyday problems this is a great site!

I am amused. This blog has just the right attitude for my current mood (spread too thin, working on too many disparate projects at once, and jealous of my student worker who gets to work on one thing at a time, at least at work.)

oracle, weblog, blog, wtf, database administration, database programming

Tom Kyte, one of the (many) good guys in the Oracle blogging community posted quite a rant a couple weeks ago. In short, Tom was disappointed with the attitude of a user who asked a broad, newbie question and was then upset when Tom’s answer was more involved than “Take two of these and call me in the morning.”

Tom’s experience reminds me that there is a right way and a wrong way to use the information on this site (and others.)

The wrong way to use information on this site:

“There’s the code I need!” copy, paste “That’s done!”

Using any commands you don’t understand in a production system should scare you. If it doesn’t, just consider what good excuse you’re going to give your boss when a system fails due to some code you just got off the internet.

The right way to use information on this site:

“That looks like what I want to do, let me read more on that and try it in a test system.” or “What was the syntax for what I’m doing?”

The information here isn’t provided to solve your problems, it is provided for educational purposes. Education and reference. While that may sound like it’s intended to lower my liability when you blow up your production database, it is; but it is also my true intention.

I am the type of person who wants to know how everything works. That doesn’t mean I won’t grab some code, throw it in a test database, see what happens, and learn from that example, but it does mean that I won’t put my job on the line with someone elses information.

Seek knowledge, not information. It takes longer to acquire, but it is far more applicable and will get you much further.

technology, oracle, information technology

If you’ve spent much time working in a UNIX environment you’ve probably seen the load averages more than a few times.

load averages: 2.43, 2.96, 3.41

I have to admit that even in my sysadmin days I didn’t fully understand what these numbers were, but Zach did some digging a while ago to try to understand where these numbers are comming from.

In his blog entry from late last year, Zach sums it up quite nicely:

In short it is the average sum of the number of processes waiting in the run-queue plus the number currently executing over 1, 5, and 15 minute time periods.

The formula is a bit more complicated than that, but this serves well as a functional definition. Zach provides a bit more detail in his article and also points out Dr. Neil Gunther’s article on the topic which has as much depth on the topic as anyone could ever ask.

So what does this mean about your system?

Well, for a quick example let’s consider the output below. The load average of a system can typically be found by running top or uptime and users typically don’t need any special privileges for these commands.

load averages: 2.43, 2.96, 3.41

Here we see the one minute load average is 2.43, five minute is 2.96, and fifteen minute load average is 3.41.

Here are some conclusions we can draw from this.

  • On average, over the past one minute there have been 2.43 processes running or waiting for a resource
  • Overall the load is on a down-trend since the average number of processes running or waiting in the past minute (2.43) is lower than the average running or waiting over the past 5 minutes (2.96) and 15 minutes (3.41)
  • This system is busy, but we cannot conclude how busy solely from load averages.

It is important here to mention that the load average does not take into account the number of processes. Another critical detail is that processes could be waiting for any number of things including CPU, disk, or network.

So what we do know is that a system that has a load average significantly higher than the number of CPUs is probably pretty busy, or bogged down by some bottleneck. Conversely a system which has a load average significantly lower than the number of CPUs is probably doing just fine.

Easy Linux CommandsFor more tips like this check out my book Easy Linux Commands, only $19.95 from Rampant TechPress.

UNIX, systems administration, sysadmin, solaris, linux, load averages, system monitoring, sun, mac, osx

« Previous PageNext Page »