Thursday, February 26, 2026
Tip of the Day: In-Memory Table Performance Boost
Product: R:BASE 11
Build: 11.0.3.20226 or higher
Section: General
Keywords: In-memory, Temporary, Temp, Tables
The in-memory table creation process has been enhanced with dynamic
memory scaling. As an in-memory table grows and requires additional
memory, the allocation request now automatically doubles in size,
significantly reducing the number of memory reallocation events during
table growth.
This improvement dramatically accelerates the creation of large
in-memory temporary tables.
*Build 11.0.3.20226 **Performance Comparison*
Row Count Prior to Build 11.0.3.20226 After Build 11.0.3.20226
100,000 rows 3.832 seconds 0.312 seconds
500,000 rows 1:25.705 (mm:ss.mmm) 0:01.206 (mm:ss.mmm)
These results demonstrate substantial performance gains, particularly as
row counts increase.
In testing scenarios involving projection of a 2-million record table,
the in-memory temporary table creation time outperformed the file-based
temporary table.
*In-Memory vs. File-Based Temporary Tables*
When deciding between in-memory and file-based temporary tables,
consider the following In-Memory Temporary Tables Advantages:
* Eliminates disk I/O for temporary file reads and writes
* Faster data access and projection
* Ideal for small to medium-sized temporary result sets
* Well-suited for repeatedly queried lookup tables
*When to Use File-Based Temporary Table*
For tables exceeding approximately 2 million records, file-based
temporary tables are recommended. While in-memory tables provide faster
access, available system memory ultimately limits capacity. File-based
temporary tables allow R:BASE to store larger data sets beyond available
memory constraints.
The Support Team
R:BASE Technologies, Inc.
https://www.rbase.com
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/rbase-l/ef9ba6dd-c8c2-39c9-155b-9e700a15bba8%40rbase.com.