Be the first to like this
The popular open source benchmark Poleposition was introduced back in 2005 to demonstrate the performance advantages of using a NoSQL, pure object-based solution as compared to traditional relational …
The popular open source benchmark Poleposition was introduced back in 2005 to demonstrate the performance advantages of using a NoSQL, pure object-based solution as compared to traditional relational mapping solutions (ORM) over RDBMS like MySQL, Postgres, etc. Recently, Poleposition has been expanded to introduce the elements of concurrency of execution and model complexity into Poleposition's core foundation circuits. The new circuits incorporate a number of NoSQL technologies which avoid the mapping overhead of breaking down the benchmark object model into relational tables and demonstrate substantial differences in performance and resource consumption. For the right kind of data models, the NoSQL technologies demonstrate order(s) of magnitude improvements in performance with demonstrateable reductions in CPU utilization and storage footprint for the RAW data.
This presentation will review those findings and draw a point of reference for when model complexity and system concurrency should impact your technology selection process in favor of NoSQL solutions capable of dealing specifically with complex information models.