The very busy server APEX.ORACLE.COM had last fall here and there performance problems ... - Why? "We can not let our loyal developers hang APEX," said the Oracle Product Development Manager Joel Kalman and rolled up his arms.
Its really very interesting research, we can read in detail in Joel's Blog .
- Webcrawler generated as additional load on the server APEX,
- 15,000 workspaces have been reduced to 8,000,
- The memory was upgraded from 16 GB to 32 GB, etc.
following topics analyzed and Joel described his solution .
1) keepalive
2)
robots.txt 3) Number of Database Access Descriptors
4) File system caching
5) Purge of Stale Workspaces
6) Memory
This may be for many their APEX server also a great help.
0 comments:
Post a Comment