1 / 8

Wildfire: A Scalable Path for SMPs E. Hagersten and M. Koster (Sun Microsystems)

Wildfire: A Scalable Path for SMPs E. Hagersten and M. Koster (Sun Microsystems). Presented by Eric Carty-Fickes February 17, 2004. Goals. Make a scalable SMP, and prove it to be better than cc-NUMA technology Run unmodified SMP apps Work well with migratory data, which cc-NUMAs don’t do

ula
Download Presentation

Wildfire: A Scalable Path for SMPs E. Hagersten and M. Koster (Sun Microsystems)

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. Wildfire: A Scalable Path for SMPsE. Hagersten and M. Koster (Sun Microsystems) Presented by Eric Carty-Fickes February 17, 2004

  2. Goals • Make a scalable SMP, and prove it to be better than cc-NUMA technology • Run unmodified SMP apps • Work well with migratory data, which cc-NUMAs don’t do • Provide a cheap solution in terms of complexity and OS mods

  3. MSMP • Gets benefits of SMPs such as better coherence miss handling • Can use large nodes to increase locality

  4. Wildfire Architecture • Network Interface Address Controller (NIAC) directs coherence communication • Perfect blocking directory

  5. Coherent Memory Replication,or CMR • S-COMA but with home addresses • Used alternately with cc-NUMA • Handled by OS, tracks remote memory cycles • Last resort for when migration can’t help • Requires significant translation hardware (local <–> global)

  6. Hierarchical Affinity Scheduler,or HAS • Keeps a process tied to its processor or node • Dynamically adjusts to load imbalance • Works well with CMR

  7. Results • vs. Origin 2K and NUMA-Q • Better for <= 28 CPUs • 2 nodes x 8 CPUs vs. 16 CPU E6K • Big improvement due to CMR and HAS • (What is relative OLTP performance?) • With tweaking, can produce “created locality,” which gives large boost

  8. Questions • Is it worth the effort to build an MSMP when scalable cc-NUMAs exist? • Isn’t writing SMP software easier, and if so, why do the NUMA flavors seem more popular?

More Related