1 / 14

SN versus SD: The Tradeoffs

SN versus SD: The Tradeoffs. Michael Stonebraker. Shared Nothing Architecture. Shared Nothing. “ Jelly bean ” nodes Local memory Local disk Connected together Typically TPC/IP But could be something else (RMDA, …). SN Proponents. All Commercial DBMSs (except Oracle). SN Features.

virginia-vin
Télécharger la présentation

SN versus SD: The Tradeoffs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SN versus SD:The Tradeoffs Michael Stonebraker

  2. Shared Nothing Architecture

  3. Shared Nothing “Jelly bean” nodes Local memory Local disk Connected together Typically TPC/IP But could be something else (RMDA, …)

  4. SN Proponents All Commercial DBMSs (except Oracle)

  5. SN Features Queries: send the query to the data; parallel query execution, if possible Compute: inside queries as user-defined functions (parallel execution, if possible) All nodes equal

  6. Shared Disk Architecture

  7. Shared Disk Any node can access any data directly through a read/write interface Popularized by Sun/HP in the 1990’s Pushed by all SAN vendors And (seemingly) by HPC community

  8. Typical HPC Configuration File server Compute server (often with small local scratch disk)

  9. Shared Disk Features Queries: send the data to the query – not vice-versa Compute: user program; disconnected from data storage Parallelism: user-controlled All nodes not equal

  10. High Level Bit Are you compute-centric and assuming you are CPU bound? Are you data-centric?

  11. My Prediction High end science (HES) will move over time to DBMSs from file systems (and low end science for that matter) to avoid drowning in “big data” and avoid encoding metadata in file names (and other bad habits)

  12. My Prediction DBMS will run SN model Way faster to utilize user-defined functions (UDFs) Over time HES will move user code to UDFs Side benefit: better share-ability

  13. My Prediction I.e. SN will win Most HPC architectures are incompatible with this future scenario Maybe all that money can be “liberated” toward a better use.

  14. Test Case Try running SS-DB on your favorite HPC!!

More Related