Skip to main content

Larry goes eXtreme!

Image
By
Two years after the moment that Oracle went into Operating Systems - Unbreakable Linux - today Larry announced that Oracle (partnering with HP) will sell hardware also. And it's not a simple commodity server... It's the HP Oracle Database Machine. This beast contains 8 database servers (with 64 cores in total) and 14 eXadata servers (with 112 cores). And an enormous amount of storage: 1400 times more than the largest iPod! I think it could contain all mp3's in the world...
An eXadata Server (officially known as the HP Oracle Exadata Programmable Storage Server) contains 2 processors with 8 cores each, 12 disks, Enterprise Linux and - and this is the coolest part - Parallel Query processing capability for every disk. By bringing processing capability close to the storage, the amount of data going through the wires from a storage server to a database server is dramatically reduced - because results are passed instead of datablocks. Because of this architecure the performance will remain the same as the database is growing - just add some more servers and it will be fine. So this is the last piece of the grid-puzzle: Next to Fusion Middleware grid and Database Grid, Oracle can provide us now with Storage Grid.
The performance of this thing is gigantic: tests proved that queries will run 10 to 50 (!) times faster than on current available hardware.
And now ofcourse the closing question: What does it cost?
A Database Machine costs $650,000 - which is $4,000 per terabyte, and that is much cheaper than other storage around. Apart from that there is 'some' license involved for the software : $1,680,000 (and surely an annual fee of 15% of that amount). So it's not for free...but it can replace a room full of yout current hardware!
Labels:

Comments

Post a Comment

Popular posts from this blog

Fix Interactive Report headers issue when using a Region Display Selector

By
When you have multiple Interactive Reports (IR) on your page and use a Region Display Selector to mimic tabs, you might notice some weird behaviour in the IR headings if you switch tabs. The headings are not positioned correctly and you get an extra empty row under the headings. It just looks weird and ugly. But if you resize your browser window, it all looks fine again (until you switch to another tab..) So can we fix this by creating a Dynamic Action that mimics that "browser window resize" event? Yes we can! Create a Dynamic Action that fires on Click of the jQuery selector li.apex-rds-item a . That should fire a JavaScript snippet :  apex.event.trigger(this.triggeringElement, "apexwindowresized"); So now a click on a tab not only switches from one IR to another but also fires that event that will "autofix" the IR headers. A simple solution for an annoying problem. This applies to APEX 5.0, I assume it will be solved in 5.1.
Post a Comment
Read more

How to create neatly formatted Excel documents using PL/SQL?

By
If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...
21 comments
Read more

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more