Mowing Oracle’s Performance Weeds
We have a local town ordinance here where I live that fines you if your grass grows above 6 inches. Lately, I’ve become really annoyed with this legacy regulation.
The higher your grass, the deeper its roots will be. Deeper roots allow your lawn to stay green with less water, and fend off insect attacks without dying off. Higher grass filters rainwater and prevents soil erosion. Tall grass actually creates a canopy of shade which shades out weeds. If you mow your lawn higher, you won’t have to cut it as often.
Some towns have increased their grass regulation heights to 8 inches. Some to 9 inches. I’ve seen some progressive towns that have even gone to 12 inches. I read one article that says Omaha, Nebraska allows 18 inches. Now at 18 inches you might just need to wear your hiking boots to go and get the paper.
But my point here is that 6 inches is a number. And just a number. It is not consistent, it isn’t right for every situation, and it is certainly not backed by any real data.
Which reminds me of some of the press releases and presentations I’ve seen from Oracle lately. No matter what the product, feature, or application, the improved performance is always claimed as 10x. It can be query performance, storage performance, response times, you name it. 10x. Have we ever seen the data behind the 10x? Is there a white paper or a benchmark where we can see the 10x? Is there a footnote that describes the 10x? And remember, it’s not 9.7x or 9.8x or even 10.1x. It’s always 10x.
I’ve thought about spending my days working to get signatures to increase my town’s 6 inch grass height ordinance. But it’s more fun to analyze Oracle data. If there was any. Oh, I’ve got to go now to mow my lawn.
The postings on this site solely reflect the personal views of the author and do not necessarily represent the views, positions, strategies or opinions of IBM or IBM management.