Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.3K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 545 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 440 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
How much maximum RAM is used by Oracle XE ?

Hi,
We are running Oracle XE on a server with 48 GB RAM out of which only 24GB is usable. I read that Oracle XE uses 2GB RAM even if more is available. This means we do not get performance increase from our server right?
Best Answer
-
XE is the free version of Oracle and has a limit to use 2Gb of RAM and 12 Gb of storage (although you can store more data than previous XE versions since you can enable compression). It also uses only 2 CPU cores:
If you need to use more RAM or Storage or CPUs in a production environment, then XE is not the edition for you,
Answers
-
XE is the free version of Oracle and has a limit to use 2Gb of RAM and 12 Gb of storage (although you can store more data than previous XE versions since you can enable compression). It also uses only 2 CPU cores:
If you need to use more RAM or Storage or CPUs in a production environment, then XE is not the edition for you,
-
In addition to spot-on comment by @L. Fernigrini , your question assumes that more memory means better performance. But if your performance bottleneck is something other than a lack of available memory, then throwing a whole terrabyte of memory at it will not improve performance one whit.
-
Thank you for both answers. It confirmed my understanding. I am transforming flat file data into rdbms, for example I am running procedure on a temp table with about 1 million records to convert dates, find certain data from other tables and inserting into actual table. This takes lot's of time even though I do it in chunks. The procedure is able to process about a thousand records per second but slows down later. That's why I wanted to know that in case of Oracle xe, increasing RAM will not be useful.
-
You should approach this just like any other performance tuning issue. Instead of jumping to some silver-bullet conclusion about what might resolve the issue, perform some actual performance analysis and see exactly where the bottleneck is. If you need help on how to perform that analysis, there is a whole forum space, here, dedicated to performance issues.
-
The procedure is able to process about a thousand records per second but slows down later.
That procedure might be very inefficently written.
-
That procedure might be very inefficently written.
Indeed.
I always refer back to a section in the Oracle7 Server Tuning, Release 7.3.3. Yes, 7.3. And it still applies.
Prioritized Steps of the Tuning Method
The recommended method for tuning an Oracle database prioritizes steps in order of diminishing returns: steps which have the greatest impact on performance are listed first. For optimal results, therefore, tackle tuning issues in the order listed: from the design and development phases through instance tuning.
Step 1: Tune the Business Rules
Step 2: Tune the Data Design
Step 3: Tune the Application Design
Step 4: Tune the Logical Structure of the Database
Step 5: Tune the SQL
Step 6: Tune the Access Paths
Step 7: Tune Memory Allocation
Step 8: Tune I/O and Physical Structure
Step 9: Tune Resource Contention
Step 10: Tune the Underlying Platform(s)
'Worrying about server memory comes under step 10 -- the very last/least priority.