Comparison: MemCP vs. MySQL - Revision history

Wikiservice: Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference

2026-08-28T10:13:55Z

Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference

← Older revision		Revision as of 12:13, 28 August 2026
Line 43:		Line 43:
	== Current measured trade-off ==		== Current measured trade-off ==

	In project measurements, OLAP and search-oriented cases have reached '''~~up to~~ 10× ~~the performance of~~ MariaDB/PostgreSQL'''. RecSets are particularly important for large filtered domains and correlated membership workflows: they carry compact record-ID sets between operators, can adapt between ranges, sparse IDs and bitmaps, and let later column scans avoid materializing wide intermediate rows.		In project measurements, OLAP and search-oriented cases have reached '''speedups of 10× and more over MariaDB/PostgreSQL'''. RecSets are particularly important for large filtered domains and correlated membership workflows: they carry compact record-ID sets between operators, can adapt between ranges, sparse IDs and bitmaps, and let later column scans avoid materializing wide intermediate rows.

	Isolated OLTP paths have taken about '''1.3–2.0× as long''' as on the established database. In complete WordPress- and wiki-style page builds, however, this has made '''no significant difference to overall page-loading time''' in the measured application workflows; the end-to-end effect depends on the application's own work and on the number and mix of SQL queries it issues. That is real optimization debt, especially for high-throughput APIs, but it is a different user impact from filtered-list ~~searches~~ over roughly one million documents ~~that~~ took around '''30 seconds on PostgreSQL'''. MemCP's immediate performance case is strongest where users wait on search, filtering, grouping and analytical reads.		Isolated OLTP paths have taken about '''1.3–2.0× as long''' as on the established database. In complete WordPress- and wiki-style page builds, however, this has made '''no significant difference to overall page-loading time''' in the measured application workflows; the end-to-end effect depends on the application's own work and on the number and mix of SQL queries it issues. That is real optimization debt, especially for high-throughput APIs, but it is a different user impact from a filtered-list search over roughly one million documents in which the same query took around '''30 seconds on PostgreSQL''' and '''1.6 seconds on MemCP'''. MemCP's immediate performance case is strongest where users wait on search, filtering, grouping and analytical reads.

	The figures are workload observations rather than a promise for arbitrary SQL. Reproduce them with the deployed versions, representative data, equal durability and successful responses; see [[Performance Measurement]].		The figures are workload observations rather than a promise for arbitrary SQL. Reproduce them with the deployed versions, representative data, equal durability and successful responses; see [[Performance Measurement]].
Line 59:		Line 59:
	Start with a copy or shadow workload rather than replacing the source of truth. Import the schema/data, run representative reads against both systems, compare results, exercise constraints and transaction conflicts, restart and restore, then measure latency and throughput. Keep MySQL available until SQL compatibility, durability, capacity, and operational rollback gates are satisfied.		Start with a copy or shadow workload rather than replacing the source of truth. Import the schema/data, run representative reads against both systems, compare results, exercise constraints and transaction conflicts, restart and restore, then measure latency and throughput. Keep MySQL available until SQL compatibility, durability, capacity, and operational rollback gates are satisfied.

	Performance and compression depend on schema, cardinality, ordering, query shape, hardware, durability mode, cache state, and concurrency. Numeric comparisons must name both versions, dataset, query, hardware, ENGINE, warm-up procedure, number of successful responses, and raw samples. The observed '''~~up to 10×~~''' ~~OLAP/search gain and~~ historical compression reductions are important evidence for MemCP's target workloads, but they are not universal guarantees.		Performance and compression depend on schema, cardinality, ordering, query shape, hardware, durability mode, cache state, and concurrency. Numeric comparisons must name both versions, dataset, query, hardware, ENGINE, warm-up procedure, number of successful responses, and raw samples. The observed '''order-of-magnitude OLAP/search gains'''—including the 30-second versus 1.6-second filtered-list case—and historical compression reductions are important evidence for MemCP's target workloads, but they are not universal guarantees.

	MemCP nevertheless aims to outperform conventional row storage for its target workloads. Publishing current losses—including application suites that remain interpreter- or compile-time-bound—is part of reaching that goal, not a reason to erase the performance proposition.		MemCP nevertheless aims to outperform conventional row storage for its target workloads. Publishing current losses—including application suites that remain interpreter- or compile-time-bound—is part of reaching that goal, not a reason to erase the performance proposition.

Wikiservice: Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference

2026-08-28T09:59:25Z

Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference

@@ Line 1: / Line 1: @@
-'''MemCP''' offers several distinct advantages compared to MySQL, making it a compelling choice for optimized database management. Read more under: [[MySQL is too slow]]
+<!-- Copyright (C) 2026 Carl-Philip Haensch -->
-=== '''No 64-Character Limit for Column Names''' ===
+MemCP is a Beta persistent main-memory, column-oriented database with MySQL protocol compatibility. It targets mixed operational and analytical workloads whose active columns benefit from compression, batch scans, and in-process APIs. It is not a complete replacement for every MySQL feature.
-=== '''Significantly Reduced Storage Requirements''' ===
+{| class="wikitable"
-MemCP reduces '''storage reqirements by 80%''' compared to MySQL's InnoDB and MyISAM storage formats. This reduction in storage demand translates to lower infrastructure costs and better scalability for large datasets.
+! Area !! MySQL !! MemCP
-=== '''Built-In Support for Natural Sorting''' ===
+== Where MemCP can be attractive ==
-=== '''Dramatic Performance Improvements''' ===
+* '''Mixed operational and analytical work:''' recent inserts and updates can feed dashboards, grouping, and ad-hoc analysis without first exporting a second analytical copy.
-MemCP delivers up to '''10x faster query performance''' for aggregation operations compared to MySQL. This makes it ideal for data-intensive applications, business intelligence workloads, and real-time analytics.
+* '''Wide tables and selective columns:''' a query can read only referenced compressed columns instead of moving whole rows through memory.
-=== '''Unified Support for OLAP and OLTP''' ===
+These are architectural opportunities, not automatic wins. Point-heavy workloads that already fit MySQL's buffer pool, write-heavy contention, poorly compressible high-cardinality values, cold remote storage, or an unsuitable physical plan may favor MySQL.
-=== '''Support for Multiple Frontends''' ===
+== Current measured trade-off ==
-By addressing common MySQL limitations and offering superior performance, MemCP positions itself as an efficient, scalable, and user-friendly alternative for modern database management needs.
+In project measurements, OLAP and search-oriented cases have reached '''up to 10× the performance of MariaDB/PostgreSQL'''. RecSets are particularly important for large filtered domains and correlated membership workflows: they carry compact record-ID sets between operators, can adapt between ranges, sparse IDs and bitmaps, and let later column scans avoid materializing wide intermediate rows.

Carli at 12:40, 4 September 2025

2025-09-04T12:40:34Z

← Older revision		Revision as of 14:40, 4 September 2025
Line 1:		Line 1:
	'''MemCP''' offers several distinct advantages compared to MySQL, making it a compelling choice for optimized database management.		'''MemCP''' offers several distinct advantages compared to MySQL, making it a compelling choice for optimized database management. Read more under: [[MySQL is too slow]]

	=== '''No 64-Character Limit for Column Names''' ===		=== '''No 64-Character Limit for Column Names''' ===

Carli at 19:47, 20 December 2024

2024-12-20T19:47:32Z

← Older revision		Revision as of 21:47, 20 December 2024
Line 5:		Line 5:

	=== '''Significantly Reduced Storage Requirements''' ===		=== '''Significantly Reduced Storage Requirements''' ===
	MemCP ~~uses only~~ '''20% ~~of the storage~~''' ~~required by~~ MySQL's InnoDB and MyISAM storage formats. This reduction in storage demand translates to lower infrastructure costs and better scalability for large datasets.		MemCP reduces '''storage reqirements by 80%''' compared to MySQL's InnoDB and MyISAM storage formats. This reduction in storage demand translates to lower infrastructure costs and better scalability for large datasets.

	=== '''Built-In Support for Natural Sorting''' ===		=== '''Built-In Support for Natural Sorting''' ===

Carli at 20:56, 19 December 2024

2024-12-19T20:56:20Z

← Older revision		Revision as of 22:56, 19 December 2024
Line 1:		Line 1:
	'''MemCP''' offers several distinct advantages compared to MySQL, making it a compelling choice for optimized database management.		'''MemCP''' offers several distinct advantages compared to MySQL, making it a compelling choice for optimized database management.

	* '''No 64-Character Limit for Column Names''' MemCP removes the restrictive 64-character limit on column names found in MySQL, allowing for more descriptive and meaningful column naming conventions.		=== '''No 64-Character Limit for Column Names''' ===
	* '''Significantly Reduced Storage Requirements''' MemCP uses only '''20% of the storage''' required by MySQL's InnoDB and MyISAM storage formats. This reduction in storage demand translates to lower infrastructure costs and better scalability for large datasets.		MemCP removes the restrictive 64-character limit on column names found in MySQL, allowing for more descriptive and meaningful column naming conventions.
	* '''Built-In Support for Natural Sorting''' MemCP supports '''natural sort order''', which arranges data logically as humans expect, such as <code>1, 2, 10, 11</code>, rather than lexicographically (<code>1, 10, 11, 2</code>). This feature works by adding collations, that support natural ordering.
	* '''Dramatic Performance Improvements''' MemCP delivers up to '''10x faster query performance''' for aggregation operations compared to MySQL. This makes it ideal for data-intensive applications, business intelligence workloads, and real-time analytics.		=== '''Significantly Reduced Storage Requirements''' ===
	* '''Unified Support for OLAP and OLTP'''MemCP combines '''Online Transaction Processing (OLTP)''' and '''Online Analytical Processing (OLAP)''' in the same database. This enables simultaneous handling of transactional and analytical workloads without the need for separate systems or data pipelines. Such flexibility enhances operational efficiency and simplifies database architecture.		MemCP uses only '''20% of the storage''' required by MySQL's InnoDB and MyISAM storage formats. This reduction in storage demand translates to lower infrastructure costs and better scalability for large datasets.
	* '''Support for Multiple Frontends'''MemCP provides support for diverse frontends, including '''SPARQL''', '''microservices''', and '''REST APIs'''. This versatility allows developers to use MemCP in various application architectures, ranging from semantic web applications to distributed microservices, ensuring seamless integration into modern development environments.
			=== '''Built-In Support for Natural Sorting''' ===
			MemCP supports '''natural sort order''', which arranges data logically as humans expect, such as <code>1, 2, 10, 11</code>, rather than lexicographically (<code>1, 10, 11, 2</code>). This feature works by adding collations, that support natural ordering.

			=== '''Dramatic Performance Improvements''' ===
			MemCP delivers up to '''10x faster query performance''' for aggregation operations compared to MySQL. This makes it ideal for data-intensive applications, business intelligence workloads, and real-time analytics.

			=== '''Unified Support for OLAP and OLTP''' ===
			MemCP combines '''Online Transaction Processing (OLTP)''' and '''Online Analytical Processing (OLAP)''' in the same database. This enables simultaneous handling of transactional and analytical workloads without the need for separate systems or data pipelines. Such flexibility enhances operational efficiency and simplifies database architecture.

			=== '''Support for Multiple Frontends''' ===
			MemCP provides support for diverse frontends, including '''SPARQL''', '''microservices''', and '''REST APIs'''. This versatility allows developers to use MemCP in various application architectures, ranging from semantic web applications to distributed microservices, ensuring seamless integration into modern development environments.

	By addressing common MySQL limitations and offering superior performance, MemCP positions itself as an efficient, scalable, and user-friendly alternative for modern database management needs.		By addressing common MySQL limitations and offering superior performance, MemCP positions itself as an efficient, scalable, and user-friendly alternative for modern database management needs.

Carli at 20:54, 19 December 2024

2024-12-19T20:54:56Z

← Older revision		Revision as of 22:54, 19 December 2024
Line 1:		Line 1:
	'''MemCP''' offers several distinct advantages compared to MySQL, making it a compelling choice for optimized database management.		'''MemCP''' offers several distinct advantages compared to MySQL, making it a compelling choice for optimized database management.

	# '''No 64-Character Limit for Column Names''' MemCP removes the restrictive 64-character limit on column names found in MySQL, allowing for more descriptive and meaningful column naming conventions.		* '''No 64-Character Limit for Column Names''' MemCP removes the restrictive 64-character limit on column names found in MySQL, allowing for more descriptive and meaningful column naming conventions.
	# '''Significantly Reduced Storage Requirements''' MemCP uses only '''20% of the storage''' required by MySQL's InnoDB and MyISAM storage formats. This reduction in storage demand translates to lower infrastructure costs and better scalability for large datasets.		* '''Significantly Reduced Storage Requirements''' MemCP uses only '''20% of the storage''' required by MySQL's InnoDB and MyISAM storage formats. This reduction in storage demand translates to lower infrastructure costs and better scalability for large datasets.
	# '''Built-In Support for Natural Sorting''' MemCP supports '''natural sort order''', which arranges data logically as humans expect, such as <code>1, 2, 10, 11</code>, rather than lexicographically (<code>1, 10, 11, 2</code>). This feature works by adding collations, that support natural ordering.		* '''Built-In Support for Natural Sorting''' MemCP supports '''natural sort order''', which arranges data logically as humans expect, such as <code>1, 2, 10, 11</code>, rather than lexicographically (<code>1, 10, 11, 2</code>). This feature works by adding collations, that support natural ordering.
	# '''Dramatic Performance Improvements''' MemCP delivers up to '''10x faster query performance''' for aggregation operations compared to MySQL. This makes it ideal for data-intensive applications, business intelligence workloads, and real-time analytics.		* '''Dramatic Performance Improvements''' MemCP delivers up to '''10x faster query performance''' for aggregation operations compared to MySQL. This makes it ideal for data-intensive applications, business intelligence workloads, and real-time analytics.
	# '''Unified Support for OLAP and OLTP'''MemCP combines '''Online Transaction Processing (OLTP)''' and '''Online Analytical Processing (OLAP)''' in the same database. This enables simultaneous handling of transactional and analytical workloads without the need for separate systems or data pipelines. Such flexibility enhances operational efficiency and simplifies database architecture.		* '''Unified Support for OLAP and OLTP'''MemCP combines '''Online Transaction Processing (OLTP)''' and '''Online Analytical Processing (OLAP)''' in the same database. This enables simultaneous handling of transactional and analytical workloads without the need for separate systems or data pipelines. Such flexibility enhances operational efficiency and simplifies database architecture.
	# '''Support for Multiple Frontends'''MemCP provides support for diverse frontends, including '''SPARQL''', '''microservices''', and '''REST APIs'''. This versatility allows developers to use MemCP in various application architectures, ranging from semantic web applications to distributed microservices, ensuring seamless integration into modern development environments.		* '''Support for Multiple Frontends'''MemCP provides support for diverse frontends, including '''SPARQL''', '''microservices''', and '''REST APIs'''. This versatility allows developers to use MemCP in various application architectures, ranging from semantic web applications to distributed microservices, ensuring seamless integration into modern development environments.

	By addressing common MySQL limitations and offering superior performance, MemCP positions itself as an efficient, scalable, and user-friendly alternative for modern database management needs.		By addressing common MySQL limitations and offering superior performance, MemCP positions itself as an efficient, scalable, and user-friendly alternative for modern database management needs.

Carli at 20:54, 19 December 2024

2024-12-19T20:54:27Z

← Older revision		Revision as of 22:54, 19 December 2024
Line 1:		Line 1:
	'''MemCP''' offers several distinct advantages compared to MySQL, making it a compelling choice for optimized database management.		'''MemCP''' offers several distinct advantages compared to MySQL, making it a compelling choice for optimized database management.

	# '''No 64-Character Limit for Column Names''' MemCP removes the restrictive 64-character limit on column names found in MySQL, allowing for more descriptive and meaningful column naming conventions.		# '''No 64-Character Limit for Column Names''' MemCP removes the restrictive 64-character limit on column names found in MySQL, allowing for more descriptive and meaningful column naming conventions.
	# '''Significantly Reduced Storage Requirements''' MemCP uses only '''20% of the storage''' required by MySQL's InnoDB and MyISAM storage formats. This reduction in storage demand translates to lower infrastructure costs and better scalability for large datasets.		# '''Significantly Reduced Storage Requirements''' MemCP uses only '''20% of the storage''' required by MySQL's InnoDB and MyISAM storage formats. This reduction in storage demand translates to lower infrastructure costs and better scalability for large datasets.
	# '''Built-In Support for Natural Sorting''' MemCP supports '''natural sort order''', which arranges data logically as humans expect, such as <code>1, 2, 10, 11</code>, rather than lexicographically (<code>1, 10, 11, 2</code>). This feature works by adding collations, that support natural ordering.		# '''Built-In Support for Natural Sorting''' MemCP supports '''natural sort order''', which arranges data logically as humans expect, such as <code>1, 2, 10, 11</code>, rather than lexicographically (<code>1, 10, 11, 2</code>). This feature works by adding collations, that support natural ordering.
	# '''Dramatic Performance Improvements''' MemCP delivers up to '''10x faster query performance''' for aggregation operations compared to MySQL. This makes it ideal for data-intensive applications, business intelligence workloads, and real-time analytics.		# '''Dramatic Performance Improvements''' MemCP delivers up to '''10x faster query performance''' for aggregation operations compared to MySQL. This makes it ideal for data-intensive applications, business intelligence workloads, and real-time analytics.
			# '''Unified Support for OLAP and OLTP'''MemCP combines '''Online Transaction Processing (OLTP)''' and '''Online Analytical Processing (OLAP)''' in the same database. This enables simultaneous handling of transactional and analytical workloads without the need for separate systems or data pipelines. Such flexibility enhances operational efficiency and simplifies database architecture.
			# '''Support for Multiple Frontends'''MemCP provides support for diverse frontends, including '''SPARQL''', '''microservices''', and '''REST APIs'''. This versatility allows developers to use MemCP in various application architectures, ranging from semantic web applications to distributed microservices, ensuring seamless integration into modern development environments.

	By addressing common MySQL limitations and offering superior performance, MemCP positions itself as an efficient, scalable, and user-friendly alternative for modern database management needs.		By addressing common MySQL limitations and offering superior performance, MemCP positions itself as an efficient, scalable, and user-friendly alternative for modern database management needs.

Carli at 20:47, 19 December 2024

2024-12-19T20:47:20Z

← Older revision		Revision as of 22:47, 19 December 2024
Line 3:		Line 3:
	# '''No 64-Character Limit for Column Names''' MemCP removes the restrictive 64-character limit on column names found in MySQL, allowing for more descriptive and meaningful column naming conventions.		# '''No 64-Character Limit for Column Names''' MemCP removes the restrictive 64-character limit on column names found in MySQL, allowing for more descriptive and meaningful column naming conventions.
	# '''Significantly Reduced Storage Requirements''' MemCP uses only '''20% of the storage''' required by MySQL's InnoDB and MyISAM storage formats. This reduction in storage demand translates to lower infrastructure costs and better scalability for large datasets.		# '''Significantly Reduced Storage Requirements''' MemCP uses only '''20% of the storage''' required by MySQL's InnoDB and MyISAM storage formats. This reduction in storage demand translates to lower infrastructure costs and better scalability for large datasets.
	# '''Built-In Support for Natural Sorting''' MemCP supports '''natural sort order''', which arranges data logically as humans expect, such as <code>1, 2, 10, 11</code>, rather than lexicographically (<code>1, 10, 11, 2</code>). This feature works ~~seamlessly with~~ collations, ~~enhancing both user experience and data presentation~~.		# '''Built-In Support for Natural Sorting''' MemCP supports '''natural sort order''', which arranges data logically as humans expect, such as <code>1, 2, 10, 11</code>, rather than lexicographically (<code>1, 10, 11, 2</code>). This feature works by adding collations, that support natural ordering.
	# '''Dramatic Performance Improvements''' MemCP delivers up to '''10x faster query performance''' for aggregation operations compared to MySQL. This makes it ideal for data-intensive applications, business intelligence workloads, and real-time analytics.		# '''Dramatic Performance Improvements''' MemCP delivers up to '''10x faster query performance''' for aggregation operations compared to MySQL. This makes it ideal for data-intensive applications, business intelligence workloads, and real-time analytics.

	By addressing common MySQL limitations and offering superior performance, MemCP positions itself as an efficient, scalable, and user-friendly alternative for modern database management needs.		By addressing common MySQL limitations and offering superior performance, MemCP positions itself as an efficient, scalable, and user-friendly alternative for modern database management needs.

Carli at 20:46, 19 December 2024

2024-12-19T20:46:04Z

← Older revision		Revision as of 22:46, 19 December 2024
Line 1:		Line 1:
	MemCP ~~has the following~~ advantages ~~over~~ MySQL:		'''MemCP''' offers several distinct advantages compared to MySQL, making it a compelling choice for optimized database management.

	* No 64 character limit for column ~~names~~		# '''No 64-Character Limit for Column Names''' MemCP removes the restrictive 64-character limit on column names found in MySQL, allowing for more descriptive and meaningful column naming conventions.
	* uses only 20% of storage ~~compared to~~ InnoDB and MyISAM storage ~~format~~		# '''Significantly Reduced Storage Requirements''' MemCP uses only '''20% of the storage''' required by MySQL's InnoDB and MyISAM storage formats. This reduction in storage demand translates to lower infrastructure costs and better scalability for large datasets.
	* supports natural sort (1, 2, 10, 11 ~~instead of~~ 1, 10, 11, 2) with collations		# '''Built-In Support for Natural Sorting''' MemCP supports '''natural sort order''', which arranges data logically as humans expect, such as <code>1, 2, 10, 11</code>, rather than lexicographically (<code>1, 10, 11, 2</code>). This feature works seamlessly with collations, enhancing both user experience and data presentation.
	* Up to 10x faster query performance for ~~aggregations~~		# '''Dramatic Performance Improvements''' MemCP delivers up to '''10x faster query performance''' for aggregation operations compared to MySQL. This makes it ideal for data-intensive applications, business intelligence workloads, and real-time analytics.

			By addressing common MySQL limitations and offering superior performance, MemCP positions itself as an efficient, scalable, and user-friendly alternative for modern database management needs.

Carli: Created page with "MemCP has the following advantages over MySQL: * No 64 character limit for column names * uses only 20% of storage compared to InnoDB and MyISAM storage format * supports natural sort (1, 2, 10, 11 instead of 1, 10, 11, 2) with collations * Up to 10x faster query performance for aggregations"

2024-12-19T20:45:02Z

Created page with "MemCP has the following advantages over MySQL: * No 64 character limit for column names * uses only 20% of storage compared to InnoDB and MyISAM storage format * supports natural sort (1, 2, 10, 11 instead of 1, 10, 11, 2) with collations * Up to 10x faster query performance for aggregations"

New page

MemCP has the following advantages over MySQL:

* No 64 character limit for column names
* uses only 20% of storage compared to InnoDB and MyISAM storage format
* supports natural sort (1, 2, 10, 11 instead of 1, 10, 11, 2) with collations
* Up to 10x faster query performance for aggregations