This HTML5 document contains 58 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dcthttp://purl.org/dc/terms/
n12https://unity.com/
dbohttp://dbpedia.org/ontology/
foafhttp://xmlns.com/foaf/0.1/
dbthttp://dbpedia.org/resource/Template:
rdfshttp://www.w3.org/2000/01/rdf-schema#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
n6http://en.wikipedia.org/wiki/
dbphttp://dbpedia.org/property/
dbchttp://dbpedia.org/resource/Category:
provhttp://www.w3.org/ns/prov#
xsdhhttp://www.w3.org/2001/XMLSchema#
dbrhttp://dbpedia.org/resource/

Statements

Subject Item
dbr:Data-oriented_design
rdf:type
owl:Thing
rdfs:label
Data-oriented design
rdfs:comment
In computing, data-oriented design is a program optimization approach motivated by efficient usage of the CPU cache, used in video game development. The approach is to focus on the data layout, separating and sorting fields according to when they are needed, and to think about transformations of data. Proponents include Mike Acton, Scott Meyers, and Jonathan Blow. The parallel array (or structure of arrays) is the main example of data-oriented design. It is contrasted with the array of structures typical of object-oriented designs.
owl:differentFrom
dbr:Data-driven_programming
dbp:wikiPageUsesTemplate
dbt:More_citations_needed dbt:Original_research_section dbt:Reflist dbt:Clarify dbt:Distinguish
dct:subject
dbc:Software_optimization dbc:Video_game_development
dbo:wikiPageExternalLink
n12:dots
prov:wasDerivedFrom
n6:Data-oriented_design?oldid=1052692314&ns=0
dbo:wikiPageID
50786173
dbo:wikiPageLength
4392
dbo:wikiPageRevisionID
1052692314
dbo:wikiPageWikiLink
dbr:Cache_(computing) dbr:Program_optimization dbr:Transistor_budget dbr:Source_code dbr:Von_Neumann_architecture dbr:Locality_of_reference dbc:Video_game_development dbr:Parallel_array dbr:Xbox_360 dbr:Central_processing_unit dbr:Out-of-order_execution dbr:AoS_and_SoA dbr:Video_game dbr:Jonathan_Blow dbr:Dynamic_dispatch dbc:Software_optimization dbr:Computing dbr:Graphics_processing_unit dbr:IBM dbr:System_bus dbr:Data_type dbr:Scott_Meyers dbr:Abstraction_layer dbr:Clock_signal dbr:CPU_cache dbr:Glossary_of_computer_hardware_terms dbr:Object-oriented_programming dbr:Data-driven_programming dbr:PlayStation_3 dbr:Entity_component_system dbr:Pipeline_(computing) dbr:PowerPC dbr:Video_game_console dbr:Itanium dbr:Field_(computer_science) dbr:Video_game_development dbr:Loop_unrolling dbr:Seventh_generation_of_video_game_consoles dbr:Memory_access_pattern dbr:Computer_data_storage
dbo:abstract
In computing, data-oriented design is a program optimization approach motivated by efficient usage of the CPU cache, used in video game development. The approach is to focus on the data layout, separating and sorting fields according to when they are needed, and to think about transformations of data. Proponents include Mike Acton, Scott Meyers, and Jonathan Blow. The parallel array (or structure of arrays) is the main example of data-oriented design. It is contrasted with the array of structures typical of object-oriented designs.
foaf:isPrimaryTopicOf
n6:Data-oriented_design