Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 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
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
Performance Issues and PCOLL_CONTROL...Help!

89163
Member Posts: 22
Hi,
We are experiencing very serious performance issues with some of our JSPs that are returning result sets greater than 1000 records (10 minutes or more). The queries are well-tuned, and it appears that the performance slows as the temporary tables are created for the application modules. We have tried adjusting the max.active.nodes and max.rows.per.node but still no improvement on performance. We have also tried setting the max.active.nodes to -1, but performance stayed the same and the temp tables were still created.
I believe we want to prevent the spillover. We do not ever expect to have more than 3000 rows returned at once, but we need to maintain optimal performance.
What does anyone recommend on either preventing the creation of the temp tables or optimizing the performance?
Thanks in advance!
Andy Hamilton
TUSC
We are experiencing very serious performance issues with some of our JSPs that are returning result sets greater than 1000 records (10 minutes or more). The queries are well-tuned, and it appears that the performance slows as the temporary tables are created for the application modules. We have tried adjusting the max.active.nodes and max.rows.per.node but still no improvement on performance. We have also tried setting the max.active.nodes to -1, but performance stayed the same and the temp tables were still created.
I believe we want to prevent the spillover. We do not ever expect to have more than 3000 rows returned at once, but we need to maintain optimal performance.
What does anyone recommend on either preventing the creation of the temp tables or optimizing the performance?
Thanks in advance!
Andy Hamilton
TUSC
Tagged:
Comments
-
The bottom of this article explains how to control/turn off the spill-over feature.
http://otn.oracle.com/products/jdev/htdocs/bc4j/bc4j_temp_tables.html
-Mark -
One option would be to use forward-only views. This would circumvente Viewcaches to take up too much space, requiring spill over to db.
-J. -
Nothing more to add here. Both of the above suggestions are what I would have said :-)
Except that by building a VO with no related entity objects (an Expert-Mode SQL-only VO) in combination with using ForwardOnly mode, you can achieve a "no caching at all" situation, neither at the EO cache level, nor the VO row level.
This would be ideal for data you only plan to render on the browser and do not need to update subsequently.
This discussion has been closed.